Network Supervisor's Toolkit

home *** CD-ROM | disk | FTP | other *** search

/ Network Supervisor's Toolkit / Network Supervisor's Toolkit.iso / novell / fyimac / walnut.fyi < prev

Wrap

Text File | 1996-07-10 | 317KB | 6,095 lines

FYI: Cannot Add Name Space to Volumes That Work Fine for DOS FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Cannot Add Name Space to Volumes That Work Fine for DOS DOCUMENT ID#: FYI.W.0230 DATE: 25SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When trying to add the Macintosh name space to a volume a variety of error messages are generated. These include: "SYS not mounted" when SYS is mounted, "The name space has already been added" when it has not, or no message is returned but the name space is not added. ISSUE/PROBLEM Some PCs with more than 16 MB have trouble with where they load their drivers in memory. SOLUTION To fix the problem, you must use the REGISTER MEMORY command before loading any drivers into memory. The problem is that the REGISTER MEMORY command must be in the AUTOEXEC.NCF file, which is not loaded from the NetWare SYS partition until after the disk driver is loaded from the STARTUP.NCF file. To resolve this, the AUTOEXEC.NCF file must be copied to the DOS partition where the STARTUP.NCF file and SERVER.EXE file is located. For example: STARTUP.NCF set minimum packet receive buffers=100 AUTOEXEC.NCF file server name Example ipx internal net 999 REGISTER MEMORY 9999999 9999999 load c:driverload c:mac Mount the rest of AUTOEXEC.NCF FYI: Cannot Save Name and Password FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Cannot Save Name and Password DOCUMENT ID#: FYI.W.0229 DATE: 25SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When logging into a NetWare for Macintosh server there is an option to Auto-Login. When this box is selected on the Macintosh workstation the following error appears: AppleShare Prep file needed some minor repairs. Some AppleShare startup information may be lost. The Macintosh does not retain the Auto-Login information, and the user must type in their name and password every time they restart the Macintosh. Even after deleting and reinstalling the AppleShare workstation software, the Macintosh will save the Auto-login information and the above error message is received. ISSUE/PROBLEM The AppleShare Prep file is where the Auto-Login information is stored. If the zone name where the file server advertises itself is "*", the AppleShare Prep file will not be able to save the Auto-Login information properly. SOLUTION Change the zone name the server advertises itself in. Do this through the LOAD APPLETLK statement. Example: LOAD APPLETLK NET=10 ZONE={"*"} Should be changed to: LOAD APPLETLK NET=10 ZONE={"Internal"} Replace "Internal" with any name other than "*". FYI: Macintosh Volume Will Not Mount FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh Volume Will Not Mount DOCUMENT ID#: FYI.W.0228 DATE: 25SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When SERVER.EXE is executed, the following error message is returned as the file server tries to mount the volume: Mounting Volume SYS Unable to Find Load file MAC.NAM Volume <volumename> Not Mounted ISSUE/PROBLEM Volumes which have Macintosh Name Space support added will not mount if MAC.NAM has not been loaded previously. Most users will have the correct LOAD MAC.NAM statement in the STARTUP.NCF, but if the MAC.NAM file is not located on the file server's DOS partition or boot disk, there is no way for NetWare to find or to load the file. SOLUTION Copy over the MAC.NAM file from the NetWare 3.11 SYSTEM-2 original disk to the same directory where STARTUP.NCF is located on the File Server's DOS partition. FYI: The APPLETLK.NLM v3.03 Does Not Register Itself as a Router on the Network. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: The APPLETLK.NLM v3.03 Does Not Register Itself as a Router on the Network. DOCUMENT ID#: FYI.W.0227 DATE: 22SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.03 SUPERSEDES: NA SYMPTOM: With 3.01 NETWARE FOR MACINTOSH (APPLETLK.NLM v3.03) installed, the NETWARE FOR MACINTOSH router doesn't register itself on the network. So, when looking in ATCON, or INTERPOLL or some other monitoring utility, the NetWare router does not appear in the list of devices on the network. Other routers (like the FastPath, Internet Router, CISCO, and basically every other AppleTalk router on the market) do register themselves as routers. ISSUE/PROBLEM The APPLETLK.NLM versions previous to 3.04 do not support this feature. SOLUTION Install APPLETLK.NLM v3.04 or above. This stack version will register itself on the network as "NetWare Router" and can be seen from within ATCON, INTERPOLL, and other similar utilities. APPLETLK.NLM v3.04 is contained in the AppleTalk Support Package on NetWire (ATSUP.ZIP). The Multi-Protocol Router uses APPLETLK.NLM v3.05, so it will also register itself as "NetWare Router" on the network. FYI: TCPort and the Asante EtherTalk SE Drivers FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: TCPort and the Asante EtherTalk SE Drivers DOCUMENT ID#: FYI.W.0226 DATE: 22SEP92 PRODUCT: TCPort PRODUCT VERSION: v1.11p1 SUPERSEDES: NA SYMPTOM: Using TCPort 1.11p1 on a Macintosh SE with the Asante EtherTalk SE interface card and drivers (previous to v4.1) hangs the Macintosh on cold boot up. Every time the Macintosh SE is "cold started" after a complete shut down, the machine hangs. The only way to get it to properly boot is to boot from a clean and simple floppy and then select "RESTART" from the "SPECIAL" menu. Asante's Macintosh II EtherTalk driver series interface cards and drivers do not experience this problem. ISSUE/PROBLEM Asante duplicated this problem and found they had a bug in their EtherTalk SE driver. SOLUTION Asante rolled the revision on the driver from v4.0 to v4.1. This version (v4.1) fixed the problem. Asante's drivers can be gotten from AppleLink under 3rd PARTY CONNECTIONS/ASANTE TECHNOLOGIES/SOFTWARE UPDATES or from the INTERNET (192.108.250.1) or you can call Asante at (1-800-622-7464) and they will send the driver through UPS blue. FYI: AFPFIX6 New Rev v1.10 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AFPFIX6 New Rev v1.10 DOCUMENT ID#: FYI.W.0217 DATE: 22SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: AFPFIX6 v1.0 SYMPTOM: If you have the AFPFIX6 v1.0 and AFP.NLM v3.01 loaded the server may abend with a GPPE and the running process is AFP. ISSUE/PROBLEM If these two NLM╒s are loaded together and there is a file with a zero byte datafork there is a possibility that the server will abend. SOLUTION What you need to do is unload the current AFPFIX6.NLM v1.0 and load this newer version of AFPFIX6.NLM v1.1. There is no need to reboot the server or unload the AFP.NLM. FYI: Changing DataClub Name FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Changing DataClub Name DOCUMENT ID#: FYI.W.0218 DATE: 17SEP92 PRODUCT: DataClub PRODUCT VERSION: NA SUPERSEDES: NA SYMPTOM: The user had an Ethernet segment and a LocalTalk segment, with a DataClub volume in each zone. Users could log in to both DataClubs, but become confused as to which DataClub volume holds which data. ISSUE/PROBLEM Change the DataClub volume name to make it unique. SOLUTION Launch the ADMINISTRATION utility. Under the DataClub menu, choose DATACLUB INFO. This dialog box allows the following 2 items to be changed: 1. The DataClub Name, as it appears in the Chooser under AppleShare. 2. The DataClub Volume Name, as it appears in the DataClub icon once DataClub is mounted on the desk top. FYI: HP Postscript Printer and ATPS Queues FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: HP Postscript Printer and ATPS Queues DOCUMENT ID#: FYI.W.0216 DATE: 17SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: When a DOS user sends a document , file, etc to an Queue serviced by ATPS to a HP Postscript Cartridge the printer would just blink like the printer was actually servicing the print job, but never printed the document or file. ISSUE/PROBLEM To service a printer of this type (HP Postscript Cartridge Plus), there are 4 modes the printer can be used in : 1) Single User Automatic 2) Single User Controlled 3) Multi User Automatic 4) Multi User Controlled Once the user decides on which mode is selected there is an appropriate TSR that must be loaded first. When Multi User Automatic mode is select one LPT port is specified to do both Postscript and PCL printing , setting the default back to Postscript when finished printing SOLUTION Selecting Multi User Controlled , which sets1 LPT port to PCL mode and the other LPT port to do Postscript Mode the problem was resolved. FYI: Error when Copying Files from Macintosh to NetWare Server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Error when Copying Files from Macintosh to NetWare Server DOCUMENT ID#: FYI.W.0215 DATE: 17SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.011, v2.2 SUPERSEDES: NA SYMPTOM: When a file is copied from a Macintosh to a NetWare v3.11 server running NetWare for Macintosh v3.011 or to a NetWare v2.2 server running NetWare for Macintosh v2.2, the following error is displayed on the Macintosh: "The file "filename" couldn't be written, because it is locked. Do you want to continue copying?" If the "Continue" button is selected, the file copies to the server, even though it appeared that it couldn't based on the error message. ISSUE/PROBLEM The above symptom occurs when a user has the Read, Create, and File Scan privileges in the folder that is being copied to. Based on the definition of these rights, the user should have sufficient rights to perform a copy from the Macintosh to the server. If the Write privilege is added to the rights the user has to the destination folder, the user can then copy a file to the server without any error message. SOLUTION The work around would be to give users Read, Write, Create, and File Scan rights to folders that they need to copy files to and from. FYI: Duplicating Desk Accessories and NetWare for Macintosh FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Duplicating Desk Accessories and NetWare for Macintosh DOCUMENT ID#: FYI.W.0214 DATE: 17SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.011 SUPERSEDES: NA SYMPTOM: When using the Duplicate command (Command-D) to duplicate a desk accessory that resides in a folder on a NetWare v3.11 server running NetWare for Macintosh v3.011, the following error is displayed on the Macintosh: "The file <filename> couldn't be written, because you do not have enough access privileges. Do you want to continue copying?" If the "Continue" button is selected, the file is NOT duplicated. ISSUE/PROBLEM The above symptoms occur when a user has Read, Create and File Scan rights to the particular folder that the duplicate command is being executed. Based on the definition of these rights, the user should have sufficient rights to perform a duplicate command. If the ALL rights are granted to the user for that particular folder, and the user tries to duplicate a desk accessory, the following error message is displayed: "You cannot duplicate in the folder <folder name>, because an error of type -39 occurred." After choosing "OK", the file IS duplicated. The error of type -39 means "end of file". This problem does not seem to occur with applications or data files...only desk accessory files duplicated from a Macintosh running system 7. SOLUTION If the user is given Read, Write, Create, and File Scan rights to a particular folder, the above error (-39) will occur, but the file is duplicated anyway. A fix to this problem may be available in a future release of the product. FYI: Silverlining with System 7 and Finder Tune-up 1.1.1 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Silverlining with System 7 and Finder Tune-up 1.1.1 DOCUMENT ID#: FYI.W.0225 DATE: 15SEP92 PRODUCT: DataClub PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: The Macintosh is crashing and freezing ISSUE/PROBLEM This is not a problem with DataClub though the user thinks that DataClub is the culprit. Silverlining v5.31 has drivers that conflict with the tune-up init. This is not a consistent problem and users may think it is the application they are running at the time that is causing the problem. SOLUTION Upgrade to Silverlining v5.4 FYI: DataClub (Changing the View) FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DataClub (Changing the View) DOCUMENT ID#: FYI.W.0224 DATE: 15SEP92 PRODUCT: DataClub PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM The default view of the DataClub is large icons. SOLUTION To change the view of the DataClub folder or any folders in DataClub you must be logged on as the owner of that folder. Example the DataClub icon folder is always owned by the administrator unless otherwise specified by the user. You log in through the Chooser on to DataClub. When it asks to connect to file server DataClub as Guest or Register User, you then key in the register user name of the owner of that folder. Example for the icon log in as register user Admin. Once you are logged on you can change the view through the Macintosh view utility. For the other users to see the changes, they must restart their Macintosh workstation. FYI: DataClub and Microsoft Works 2.0 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DataClub and Microsoft Works 2.0 DOCUMENT ID#: FYI.W.0223 DATE: 15SEP92 PRODUCT: DataClub PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: When using Microsoft Works v2.0 with DataClub there are two known problems. 1. You go to save a updated document and it will only let you do a SAVE AS instead of a SAVE command. 2. You save a new document and when you to update that document after saving it shows up as 0 KB in size. The application never saved it. ISSUE/PROBLEM The problem with Works 2.0 is that it treats the Macintosh 32-bit directory IDs as 16-bit directory. SOLUTION Microsoft is aware of this problem and is working on a solution. FYI: Could Not Recreate Desktop FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Could Not Recreate Desktop DOCUMENT ID#: FYI.W.0222 DATE: 15SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: Receiving the following error messages when trying to load AFP CDT: 1. AFPMODULE created DESKTOP.AFP on volume <volume name>. 2. AFPMODULE error updating ICON INDEX in desktop file ICONINDX.AFP. 3. AFPMODULE could not properly initialize desktop file ICONINDX.AFP on volume <volume name>. 4. AFPMODULE could not initialize AFP support on volume <volume name>. 5. No DTVPtr Memory ISSUE/PROBLEM There was not enough space to create the desktop. VOLINFO showed that there was available space on the volume; however, DIR showed no available space. The user checked DSPACE and a directory limit was set. SOLUTION Removing this directory limit in DSPACE allowed the user to successfully load AFP CDT. FYI: NetWare for Macintosh v3.01 Printing Errors FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare for Macintosh v3.01 Printing Errors DOCUMENT ID#: FYI.W.0221 DATE: 15SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: Receiving PostScript exception errors on the banner page when attempting to print through a NetWare for Macintosh queue. When the printer was restarted and SYS:SYSTEM\ATPS\APP710.PRS was deleted, the first print job through the queue printed correctly. However, the next job generated PostScript exception errors. ISSUE/PROBLEM The ATPSFIX2 patch is necessary to resolve this issue. While this patch was loaded on the file server, it was loaded before ATPS and therefore could not fix the ATPS NLM. SOLUTION Load ATPS before loading ATPSFIX2. Be sure that, when unloading these NLMs, ATPSFIX2 is unloaded before ATPS. FYI: WordPerfect and System 7 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: WordPerfect and System 7 DOCUMENT ID#: FYI.W.0220 DATE: 15SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: Receiving error "Disk is full. Please free up some space on the volume that contains the temporary files" when trying to launch the WordPerfect application off of a local hard drive. There was plenty of available space on this hard drive. No NetWare volumes were mounted at the time of the error receipt. ISSUE/PROBLEM This is a reported problem with WordPerfect Corporation. This error is generated when any sort of hardware or software change occurs on a Macintosh running System 7. In this instance, the user had recently installed new Token-Ring drivers. SOLUTION To resolve this problem, go to the Control Panel into Sharing Setup and assign an owner name and a Macintosh name. The WordPerfect application looks to this location to learn where it should store its temporary files. FYI: HP LaserJet IID and PSERVER FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: HP LaserJet IID and PSERVER DOCUMENT ID#: FYI.W.0219 DATE: 15SEP92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.011 SUPERSEDES: NA SYMPTOM: Receiving the erroneous error Printer out of Paper in PCONSOLE when trying to print from a PC to an HP LaserJet IID connected to a parallel port on the file server. The user was using the PSERVER.NLM v1.22. ISSUE/PROBLEM There is a problem with v1.22 of the PSERVER.NLM that will cause this error. SOLUTION To resolve this problem, load the PSERVER.NLM version 1.22r and the erroneous error message will stop appearing. Therefore, printing from a PC will no longer be suspended. FYI: Leading Zeros with AppleTalk NET Numbers FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Leading Zeros with AppleTalk NET Numbers DOCUMENT ID#: FYI.W.0204 DATE: 21AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0x SUPERSEDES: NA SYMPTOM: The network number shown in the Router Interfaces screen of ATCON is not the same as the network number on the Load APPLETLK line of the AUTOEXEC.NCFfile. ISSUE/PROBLEM NetWare for Macintosh uses the standard C Library call to read input from the user. In the standard C Library and "x" means read the number in as hex and a leading "0" means read the number in as Octal. For example: Load APPLETLK Net=0204 Zone={"Admin"} Everything will load properly but viewing Router Interfaces from within Atcon would show 132-132 as the Internal network number. The Octal number 0204 is converted to 132 in Decimal and is a valid APPLETLK network number. SOLUTION Do not use Octal numbers on the Load APPLETLK or Bind APPLETLK lines in the AUTOEXEC.NCF file when using NetWare for Macintosh. FYI: PSERVER.NLM 1.22 and ATPS FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: PSERVER.NLM 1.22 and ATPS DOCUMENT ID#: FYI.W.0213 DATE: 20AUG92 PRODUCT: NetWare for Macintosh (ATPS) PRODUCT VERSION: 3.01 SUPERSEDES: NA SYMPTOM: Every time a Macintosh print job is sent to the PSERVER.NLM (1.22) queue, the job sticks in the queue as READY. When looking at the PSERVER.NLM monitor, it says it is waiting for the next print job. When the DOS user sends a job to the same queue, it prints ahead of the Macintosh job (which stays in the READY state). The only way to get the Macintosh job to print is to select the job from within PCONSOLE (Print Queue Information\Print Queues\Current Print Job Entries) then change the FORM name (from Normal to one of the other FORMS). ISSUE/PROBLEM When the NetWare print server is installed and configured from PCONSOLE, there are quite a few parameters to handle. Because Macintosh clients use this print server (assuming the ATPS -wb option is in use), these settings can and do affect print jobs that are sent to queues which are serviced by the PSERVER.NLM print server. SOLUTION The print server had been configured to "SERVICE ONLY CURRENTLY MOUNTED FORMS." When this parameter was changed to "CHANGE FORMS AS NEEDED," all worked fine. To change this "forms parameter," do the following: 1. Get into PCONSOLE, "Print Server Information" menu. 2. Select the appropriate print server in the "Print Server Configuration" menu "Printer Configuration" option. 3. Select the printer from the "Queue Service Mode" option. 4. Select the "Change Forms as needed" option. 5. When changes like this are made to the print server, be sure to UNLOAD/LOAD PSERVER.NLM. If this is not done, the changes will not take affect. FYI: Logging in with Invalid User Name FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Logging in with Invalid User Name DOCUMENT ID#: FYI.W.0203 DATE: 20AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0x SUPERSEDES: NA SYMPTOM: When logging in to a NetWare for Macintosh file server via AppleShare, user names that include spaces in them are still allowed to login but the password cannot be changed. ISSUE/PROBLEM For example: If the user "Supervisor" logs in to a 3.0x NetWare for Macintosh file server via AppleShare and mistypes his name as "Supervisor" the file server will still accept this user name and password and allows the user to mount volumes without a problem. This is because the NetWare file server removes the spaces in the user name. After the user has logged into the file server using this faulty ID, the user tries to change the password by clicking on SET PASSWORD in the Chooser's AppleShare utility. The user can type the old and new password but will receive the following message because the user's ID is invalid: "Your password could not be changed. Please try again or see your system administrator" SOLUTION When logging in via AppleShare, do not use any spaces in the user name. FYI: Server Reboots when Loading NetWare for Macintosh v3.01 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Server Reboots when Loading NetWare for Macintosh v3.01 DOCUMENT ID#: FYI.W.0202 DATE: 18AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: Server configured with NetWare v3.11 on a PS/2 Model Portable with a Cabletron E3010 NIC. When booting the server with the NetWare for Macintosh v3.01 NLMs, the server would reboot itself once the "server registered with NBP" message would appear on the screen. ISSUE/PROBLEM Found out that the STARTUP.CFG did not contain the following line: "set minimum packet receive buffers=100" SOLUTION Set the minimum packet receive buffers to 150, rebooted the server, everything worked properly. FYI: Slow TCPort Performance on Macintosh IIfx FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Slow TCPort Performance on Macintosh IIfx DOCUMENT ID#: FYI.W.0201 DATE: 18AUG92 PRODUCT: LAN WorkPlace for Macintosh PRODUCT VERSION: v1.11 SUPERSEDES: NA SYMPTOM: A delayed response was seen when typing information into a Telnet session running Host Access and TCPort v1.11. ISSUE/PROBLEM There have been many compatibility issues with TCPort v1.11 and some of the newer/faster Macintosh models. SOLUTION A new version of the TCPort driver is available on NetWire or NetWare Express called TCPIP.SIT. This new version fixed the problem. FYI: Mylex LNE390 New Driver Available that Supports Ethernet_snap FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Mylex LNE390 New Driver Available that Supports Ethernet_snap DOCUMENT ID#: FYI.W.0200 DATE: 18AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: Having problems with the Mylex LNE390 card not working properly with the Ethernet_Snap frame type. When the server boots up everything appears to have loaded properly, but the Macintoshes on the network cannot see the server. ISSUE/PROBLEM Checked with Mylex for a possible new driver, and a new beta driver is available now. After downloading the newer driver and loading it on the server, everything has been working great ever since. Note: The new driver has the same version and date as the older one. The only thing that is different is the size: Old: Mylex v3.10 (910911) size = 12919 bytes New: Mylex v3.10 (910911) size = 14505 bytes The README file with the new driver is dated 05-07-92. The name of the LAN driver has also changed:LNE390.LAN is for NetWare v3.10LNE31.LAN is for NetWare v3.11. Mylex's BBS number is 510-793-3491. SOLUTION Download the new v3.10 (14505 bytes) driver from Mylex BBS. FYI: LAN WorkPlace for Macintosh Support for RPC Libraries FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LAN WorkPlace for Macintosh Support for RPC Libraries DOCUMENT ID#: FYI.W.0199 DATE: 18AUG92 PRODUCT: LAN WorkPlace for Macintosh PRODUCT VERSION: v1.11 SUPERSEDES: NA SYMPTOM: Does LAN WorkPlace for Mac support RPC (Remote Procedure Calls) Libraries? ISSUE/PROBLEM RPCs behave like subroutines, except the subroutine is executing on another machine, or remotely. For example, say subroutine foo1 calls subroutine foo2. In a "normal" application, the code for foo1 is linked together with the code for foo2, thus placing the code in one location. In an RPC, the compiler would know that foo2 is actually a "remote" call and would create the necessary code to communicate over a network to another host. The other host would have the code to run foo2. SOLUTION NO, LAN WorkPlace for Macintosh does not support RPC Libraries! FYI: Fast PC and DL2000 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Fast PC and DL2000 DOCUMENT ID#: FYI.W.0205 DATE: 12AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: Macintosh cannot see the server or LaserWriter printers. ISSUE/PROBLEM If a Dayna DL2000 is in a very fast PC with a fast bus speed, such as a 486 running at 50Mhz, the DL2000 may not function properly. SOLUTION This can be verified by typing "config" at the server's console prompt. If the DL2000 is functioning, the twelve digit node address should be 000000000080, if this number is all zeros, try bringing up the server at a slower speed. If the node address is still all zeros the card may be defective. FYI: Personal LaserWriter LS and LaserWriter II SC FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Personal LaserWriter LS and LaserWriter II SC DOCUMENT ID#: FYI.W.0198 DATE: 12AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0x SUPERSEDES: NA SYMPTOM: Cannot get the Apple LaserWriter LS or the LaserWriter IISC to work as network printers. ISSUE/PROBLEM The Apple Personal LaserWriter LS and the LaserWriter II SC will not work as network printers. The printers are not PostScript and do not have an AppleTalk connection. These printers will also not work with PSERVER or RPRINTER either. The 3.01 Installation and Maintenance manual on page 9 includes these printers in the list of supported printers but this is incorrect. SOLUTION Upgrade the printers to a LaserWriter NT model for use as network printers. FYI: LAN Work Place for Macintosh and BOOTP Server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LAN Work Place for Macintosh and BOOTP Server DOCUMENT ID#: FYI.W.0197 DATE: 12AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM: TCPort is not getting a dynamic IP address from a BOOTP server. ISSUE/PROBLEM When trying to use a BOOTP server to assign IP addresses to workstations on the network, it will not work with TCPort because the BOOTP server was more than one hop away. LAN WorkPlace for Macintosh sets the Time-to-Live field in the IP header to 2 (seconds) which is not long enough to work with a BOOTP server which is more than one hop away. SOLUTION If a Macintosh with v1.1 of TCPort is going to get a dynamic address from a BOOTP server, the BOOTP server must reside on the same Ethernet cable as the TCPort Macintosh (page 84 to 85 of LAN WorkPlace for Macintosh manual). No support for a BOOTP server is available before LAN WorkPlace for Macintosh v1.1. FYI: 7.1 LaserWriter Driver FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: 7.1 LaserWriter Driver DOCUMENT ID#: FYI.W.0196 DATE: 12AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When printing to a NetWare for Macintosh print queue with the 7.1 version of the LaserWriter driver, nothing is printed. ISSUE/PROBLEM If ATPS is in the -wb mode and a Macintosh with the 7.1 LaserWriter driver prints to the queue, ATPS gives the job to the print server but the printer just blinks a few times and nothing prints. SOLUTION Put the 7.0 LaserWriter driver on the Macintosh or get the ATPSFIX2 patch from NetWire or NetWare Express. The file is ATPS2.ZIP. FYI: Printing with PageMaker 4.2 and Binary PostScript FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printing with PageMaker 4.2 and Binary PostScript DOCUMENT ID#: FYI.W.0212 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: When printing a job from PageMaker 4.2, the printer ready light blinks and blinks as if it is receiving the print job data, but nothing prints out (not even a PostScript error page). The job is removed from the queue because NetWare perceives that the job has printed correctly. ISSUE/PROBLEM Configuration: The PostScript printer (such as HP IIIsi, QMS, NEC SilentWriter, Apple LaserWriter IINT) is configured as a PSERVER or RPRINTER printer attached via the parallel or serial port. When graphics in the PageMaker 4.2 print job are sent as "binary postscript" data over a non-Appletalk channel (such as a non-binary channel), the binary control characters which represent the graphics are interpreted as printer control characters (0x14 = "request printer status," 0x4 = "end of job") and interfere with the printing of the job. SOLUTION In PageMaker 4.2, Binary printing can be turned off to avoid the above mentioned problems: 1. Select "Print" from the File Menu 2. Select the "PostScript" option 3. There will be an option for Send Image Data with two options available: - Faster (Binary) - Normal (Hex) 4. Select "Normal (Hex)"Unfortunately, this option cannot be saved as a default setting and must be selected each time a job is printed. This option is not available in versions of PageMaker earlier than v4.2. FYI: SMC EISA 3032 Does Not Support AppleTalk Phase 2 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: SMC EISA 3032 Does Not Support AppleTalk Phase 2 DOCUMENT ID#: FYI.W.0211 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: A Macintosh workstation tries to log in, but the file server name does not show up in the chooser. ISSUE/PROBLEM AppleTalk Phase 2 packets are not being broadcast in a correct format from the File Server. Even though it appears that the Ethernet_SNAP frame type is loading and AppleTalk is being bound correctly to the SMC EISA 3032, it is not. SMC Technical Support confirmed that while their current driver does support ETHERNET_SNAP frame type, it does NOT support Multicasting and, therefore, the SMC EISA 3032 does NOT support AppleTalk Phase 2. SOLUTION Use AppleTalk Phase 1 (Ethernet_II frame type) or use a different Ethernet card that does support AppleTalk Phase 2, like the NE3200, NE2000, or 3C505. SMC Technical Support can be reached at 800-992-4762 or 516-273-3100. FYI: Kodiak Technology Raven-16 Does Not Support Ethertalk Phase 2 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Kodiak Technology Raven-16 Does Not Support Ethertalk Phase 2 DOCUMENT ID#: FYI.W.0210 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: From a Macintosh workstation, a Macintosh user wants to change from the Built-in Localtalk port to their EtherTalk port by selecting Control Panel and Network. When the EtherTalk Phase 2 icon is selected, the following messages are displayed: "Access to your AppleTalk internet has now become available. To use the internet, please click the Network icon in the Control Panel, then click the selected AppleTalk connection icon." The User then clicks OK and receives a message saying: "You cannot choose a zone at this time because no internet router is available." When the user clicks OK, the user receives the following message: "Access to your AppleTalk internet has now become available ..." Then the user clicks OK, and gets a message saying the following and is in this loop: "You cannot choose a zone at this time because no internet router is available" The user is never able to select a default zone for the Macintosh workstation and cannot log into the file server. ISSUE/PROBLEM AppleTalk Phase 2 packets are not being broadcast in a correct format from the File Server. Even though it appears that the Ethernet_SNAP frame type is loading and AppleTalk is being bound correctly to the Kodiak Raven-16, it is not. Kodiak Technology Technical Support confirmed that their current driver does not support AppleTalk Phase 2. SOLUTION Kodiak currently has a Beta driver (v1.80) that is has been revised to support AppleTalk Phase 2. Contact Kodiak Technical Support to obtain the Phase 2 Beta driver or use AppleTalk Phase 1 (Ethernet_II frame type). Kodiak Technical Support can be reached at 800-777-7704 or 408-441-6900. FYI: Loader Cannot Find Public Symbol: (Various PUBILIC File Names) FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Loader Cannot Find Public Symbol: (Various PUBILIC File Names) DOCUMENT ID#: FYI.W.0209 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: User loads AFP.NLM and receives the following errors: Loader cannot find public symbol: asp_init Loader cannot find public symbol: asp_cmdreply Loader cannot find ....... ... (many other similar errors occur ... ... referencing different public symbols) Load file referenced undefined public variable Module AFP.NLM not loaded User loads ATPS.NLM and receives the following errors: Loader cannot find public symbol: asp_get_NWConnID from AT address Loader cannot find public symbol: nbp_lookup Loader cannot find ....... ... (many other similar errors occur ... ... referencing different public symbols) Load file referenced undefined public variable Module ATPS.NLM not loaded User loads ATCON.NLM and receives the following errors: Loader cannot find public symbol: at_rtr_buf_stats Loader cannot find public symbol: at_rtr_snmp_start Loader cannot find ....... ... (many other similar errors occur ... ... referencing different public symbols) Load file referenced undefined public variable Module ATCON.NLM not loaded User Loads V_MAC.NLM and receives the following errors: Loader cannot find public symbol: nameSpaceSupported Loader cannot find public symbol: nameSpaceNLMHandle Loader cannot find ....... ... (many other similar errors occur ... ... referencing different public symbols) Load file referenced undefined public variable Module V_MAC.NLM not loaded ISSUE/PROBLEM The current NLM module (AFP, ATPS, ATCON or V_MAC) depends upon another NLM to have been loaded previously but has not been loaded. SOLUTION In the case of loading AFP, ATPS or ATCON, the errors are likely a result of APPLETLK.NLM not being loaded correctly. Type the MODULES command at the file server console prompt to verify if the APPLETLK.NLM is currently loaded. If the module has not loaded correctly, check for syntax errors or misspelled words in the LOAD APPLETLK statement. In the case of loading V_MAC, VREPAIR needs to be loaded before V_MAC. 1. Dismount the volume which needs the VREPAIR operation. 2. Load VREPAIR. 3. Press <Ctrl>+<Esc> and select the System Console. 4. Then Load V_MAC. 5. Press <Ctrl>+<Esc> to return to VREPAIR and continue with the VREPAIR operation. FYI: Desktop Files are Invalid or Damaged FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Desktop Files are Invalid or Damaged DOCUMENT ID#: FYI.W.0208 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: When AFP.NLM is loaded, the following error occurs: Desktop Files are Invalid or Damaged. ISSUE/PROBLEM The Desktop files are hidden files located on the NetWare volume used by the Macintosh operating system. The Desktop holds information regarding which documents are related to which applications and also holds the icon information for each file. The error "Desktop Files are Invalid or Damaged" indicates that the Desktop has become damaged and needs to be repaired. SOLUTION A two step operation which is necessary to repair the desktop is listed below: 1. Unload AFP and then type LOAD AFP CDT This option clears the Desktop files, replacing the existing (damaged) Desktop files with new Desktop files. 2. To rebuild the information that the Desktop saves, login as Supervisor from a Macintosh workstation running System 6.0.X in Finder. As you mount the NetWare file server volume, hold down the Option and Command keys. A window will be displayed asking if you want to rebuild the desktop. This operation should be performed for each volume on the file server that has Macintosh name space support. FYI: PAPFIX1.NLM and Error: Invalid modification record found in modList FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: PAPFIX1.NLM and Error: Invalid modification record found in modList DOCUMENT ID#: FYI.W.0207 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: With NetWare 3.11 - 100 user version and NetWare for Macintosh v3.0, the error "Invalid modification record found in modList" is received when trying to load PAPFIX1.NLM. ISSUE/PROBLEM There are two versions of the PATCHMAN.NLM - the original is dated 04-21-91, the newer version is dated 10-10-91. There are also two version of PAPFIX1.NLM - the original is dated 04-26-91, the newer version is dated 12-02-91. The original PAPFIX1.NLM (04-26-91) was written to run with the original version of PATCHMAN.NLM (dated 04-21-91). This error will occur if you load the original version of PAPFIX1.NLM with the new version of PATCHMAN.NLM. SOLUTION Use the revised version of PAPFIX1.NLM dated 12-2-91 which has been written to run with the new PATCHMAN.NLM (dated 10-10-91). Make sure that both the PATCHMAN.NLM and PAPFIX1.NLM are the revised versions. FYI: PAPFIX1.NLM and Error: Does Not Support 250 User Version of NetWare FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: PAPFIX1.NLM and Error: Does Not Support 250 User Version of NetWare DOCUMENT ID#: FYI.W.0206 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: With NetWare v3.11 - 250 user version and NetWare for Macintosh v3.0, the error "Does not support 250 user version of NetWare" is received when trying to load PAPFIX1.NLM. This installation has always had the 250-user version of NetWare v3.11 and did not have any previous problems loading the PAPFIX1.NLM patch previously. ISSUE/PROBLEM There are two versions of the PATCHMAN.NLM - the original is dated 04-21-91, the newer version is dated 10-10-91. There are also two versions of PAPFIX1.NLM - the original is dated 04-26-91, the newer version is dated 12-02-91. The original PAPFIX1.NLM (04-26-91) was written to run with the original version of PATCHMAN.NLM (dated 04-21-91). This error will occur if you load the original version of PAPFIX1.NLM with the new version of PATCHMAN.NLM. SOLUTION Use the revised version of PAPFIX1.NLM dated 12-02-91 which has been written to run with the new PATCHMAN.NLM (dated 10-10-91). Make sure that both the PATCHMAN.NLM and PAPFIX1.NLM are the revised versions. FYI: NCR ADP-37-01 Disk Controllers and AppleTalk Traffic FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NCR ADP-37-01 Disk Controllers and AppleTalk Traffic DOCUMENT ID#: FYI.W.0195 DATE: 10AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When a user copied a file from their local Macintosh hard drive to a NetWare v3.11 file server, the file name would have its last character changed to a random alphanumeric character. For example: If a copy was attempted of "MYFILE" from a local Macintosh to the file server, the file server would advertise this file as "MYFILx", where x would be any random alphanumeric character. During limited tests, MYFILE would appear as MYFILx, MYFILT or MYFILW. This would also happen if a copy was made from one file server to another. In addition, if a user made a duplicate of a file, the "Copy of..." file would include one or two spaces at the beginning of the file name. For example: The original file was "MYFILE", but if a duplicate was made, the second file would be " MYFILE" or " MYFILE" ISSUE/PROBLEM The data integrity of the file remained intact; it was only that the file name had been changed. The user had NCR ADP-37-01 disk controllers installed in their file server, which was running v01.05 of the ROM BIOS. NCR technical support suggested that these controllers had inconsistencies with AppleTalk traffic and there was an upgrade to the driver along with the BIOS. SOLUTION NCR technical support sent the user a newer disk driver (ADP37.DSK) along with v01.06 of the ROM BIOS, which resolved the problem. FYI: Mapping and Login Scripts FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Mapping and Login Scripts DOCUMENT ID#: FYI.W.0194 DATE: 07AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.011 SUPERSEDES: NA SYMPTOM: Receiving error: "Could not execute external command" ISSUE/PROBLEM When trying to login as supervisor, the user was getting the error listed above. The system login script consisted only of a capture statement. No user login script existed. The user was able to use the capture command when at a DOS prompt. SOLUTION When the user gave the full server and directory path to the CAPTURE command in the system login script, logging in as supervisor was successful. The cause of this problem was that there was not an exit statement in the system login script and the user was not using a user login script. The combination of these two factors was causing the default mappings that are in LOGIN.EXE to be used; that of Y: and Z:. Therefore, because the CAPTURE command was attempted before any mappings occurred, it was not being found. Giving CAPTURE.EXE a full path allowed it to be found. FYI: Loading Appletalk Error FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Loading Appletalk Error DOCUMENT ID#: FYI.W.0193 DATE: 07AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: Receiving error" "AppleTalk stack router xxxxx did not start up correctly" ISSUE/PROBLEM When attempting to load APPLETLK, the suer was getting the error listed above. SOLUTION The user was not defining an internal zone; i.e. the AUTOEXEC.NCF had the following load line:load APPLETLK -t net=5005Changing the line to:load APPLETLK -t net=5005 zone={"Internal"}allowed APPLETLK to load successfully. FYI: Lanstor 7 Drivers FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Lanstor 7 Drivers DOCUMENT ID#: FYI.W.0192 DATE: 07AUG92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.011 SUPERSEDES: NA SYMPTOM: Receiving error "Error reading from load file when trying to load the Macintosh name space from the DOS partition of the hard drive. ISSUE/PROBLEM When attempting to load the Macintosh name space from the DOS partition of the hard drive, the user was getting the error listed above. However, the name space auto-loaded anyway. The user was able to successfully load the same exact MAC.NAM from the floppy drive. Even when the "load mac" statement was removed from the STARTUP.NCF and the server was rebooted, the name space was auto-loaded. SOLUTION This is a reported problem with Storage Dimensions. The temporary workaround is to do the following: 1. Reverse the order of the STARTUP.NCF statements, so that the name space is loaded before the Lanstor driver. 2. Have the AUTOEXEC.NCF on the DOS partition of the server and manually input the server's name.Executing both of these two steps allowed the user to load the Macintosh name space correctly. FYI: LAN WorkPlace for Macintosh and the Dayna EZ SCSI Adapter FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LAN WorkPlace for Macintosh and the Dayna EZ SCSI Adapter DOCUMENT ID#: FYI.W.0191 DATE: 06AUG92 PRODUCT: LAN WorkPlace for Macintosh PRODUCT VERSION: 1.11 SUPERSEDES: NA SYMPTOM: After installing LAN WorkPlace for Macintosh on my PowerBook, TCPort will not load. ISSUE/PROBLEM This is a known problem with the Dayna EZ SCSI Ethernet adaptor. It will not attach the PowerBook to the Ethernet network at boot time. After the PowerBook boots, the user must reselect the EtherTalk icon in the Network portion of the Control Panel. Since the PowerBook is not attached to the network at boot time, TCPort cannot load. SOLUTION Dayna is aware of this problem and is working on a solution. For more information, Dayna can be reached at 801-531-0600. FYI: LAN WorkPlace for Macintosh and the PowerBook FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LAN WorkPlace for Macintosh and the PowerBook DOCUMENT ID#: FYI.W.0190 DATE: 06AUG92 PRODUCT: LAN WorkPlace for Macintosh PRODUCT VERSION: 1.11 SUPERSEDES: NA SYMPTOM: After installing LAN WorkPlace for Macintosh on my PowerBook workstation, it will not load TCPort. ISSUE/PROBLEM This is a known problem with TCPort v1.x and the PowerBook. SOLUTION Upgrade to v2.2.1 of TCPort. TCPort v2.2.1 can be obtained through NetWire, AppleLink, and the NSEPro. FYI: LAN WorkPlace for Macintosh and the Quadra FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LAN WorkPlace for Macintosh and the Quadra DOCUMENT ID#: FYI.W.0189 DATE: 06AUG92 PRODUCT: LAN WorkPlace for Macintosh PRODUCT VERSION: 1.11 SUPERSEDES: NA SYMPTOM: After installing LAN WorkPlace for Macintosh on my Quadra, it will not work with the built-in Ethernet port. ISSUE/PROBLEM This is a known problem with TCPort v1.x and the Quadra. SOLUTION Upgrade to v2.2.1 of TCPort. TCPort v2.2.1 can be obtained through NetWire, AppleLink, and the NSEPro. FYI: LAN WorkPlace for Macintosh and System 7 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LAN WorkPlace for Macintosh and System 7 DOCUMENT ID#: FYI.W.0188 DATE: 06AUG92 PRODUCT: LAN WorkPlace for Macintosh PRODUCT VERSION: 1.11 SUPERSEDES: NA SYMPTOM: After installing LAN WorkPlace for Macintosh on my System 7 workstation, Domain Name Services does not work. The name is not resolved. ISSUE/PROBLEM This is a known problem with TCPort v1.x and System 7 Macintoshes. This can also happen with v2.2.1 TCPort if it is installed in the Control Panel folder instead of at the root of the System folder. SOLUTION Upgrade to v2.2.1 of TCPort or move v2.2.1 TCPort to the root of the System folder on the Macintosh. TCPort v2.2.1 can be obtained through NetWire, AppleLink, and the NSEPro. FYI: Multiple Print Copies to a NetWare Print Queue FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Multiple Print Copies to a NetWare Print Queue DOCUMENT ID#: FYI.W.0187 DATE: 22JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.x and v3.x SUPERSEDES: NA SYMPTOM: When a Macintosh prints multiple copies to a print queue that is servicing a pre-LaserWriter NTX (such as LaserWriter NT), the job may print out multiple times. ISSUE/PROBLEM According to Apple this is a known bug with pre-LaserWriter NTXs. SOLUTION Upgrade the printer to a LaserWriter NTX or do not print multiple. Contact Apple Computer for more information. FYI: DataClub and Radius Driver Versions FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DataClub and Radius driver versions DOCUMENT ID#: FYI.W.0186 DATE: 21JUL92 PRODUCT: DataClub PRODUCT VERSION: Any SUPERSEDES: NA SYMPTOM: When executing DataClub on a Macintosh that has a Radius Accelerator 025 or 030 board, the Macintosh does not see any other Macintosh machines on the network and acts as a stand-alone system. ISSUE/PROBLEM A problem exists with the Radius Accelerator card's driver. Versions previous to v2.8 are not network compatible. SOLUTION Upgrade to the v2.8 (or newer) Radius driver. FYI: DOS Workstation ODI Drivers for AppleTalk FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DOS Workstation ODI Drivers for AppleTalk DOCUMENT ID#: FYI.W.0185 DATE: 20JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM Are there AppleTalk ODI drivers for DOS workstation Ethernet cards? Can multiple protocols, AppleTalk, IPX, or IP be bound to an NE2000 card in a DOS workstation (not the File Server) in order to access various kinds of hosts and servers? SOLUTION IPX and IP can be used with the ODI NetWare work station drivers. For AppleTalk support, Farallon Computing (Emeryville, CA) has an ODI AppleTalk driver, but it only works with the 3COM 3C503 EtherLink and the 3COM 3C523 EtherLink MC Ethernet cards. Farallon may have support for the NE2000 and other Ethernet boards in a future release later this year (1992) and does support their own LocalTalk board in the DOS workstation. Farallon's Technical Support can be reached at 510/596-9000. FYI: Server GPPE ABEND in Product Options-INSTALL.NLM FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Server GPPE ABEND in Product Options-INSTALL.NLM DOCUMENT ID#: FYI.W.0184 DATE: 20JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: When selecting Product Options in INSTALL.NLM, the file server GPPE ABENDS and results in the following error messages: Unable to Open transaction file Abnormal NLM Termination Module NetWare 386 BTrieve Record Manager GPPE: Running Process Install Process ISSUE/PROBLEM The INSTALL.NLM uses NetWare BTRIEVE to keep track of which Product NLMs have been installed. The BTRIEVE.NLM tries to open the BTRIEVE transaction control file, BTRIEVE.TRN, but cannot because it is flagged "RO" incorrectly or is corrupted. SOLUTION Use the FLAG command to reflag the BTRIEVE.TRN as "RW." Also double check to make sure that a current version of BTRIEVE.NLM (02/19/91 or later) is being used. Using a version of BTRIEVE from NetWare 3.0 or NetWare 3.1 software will also result in a Server ABEND. FYI: QuarkXpress and Printing with Binary PostScript FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: QuarkXpress and Printing with Binary PostScript DOCUMENT ID#: FYI.W.0183 DATE: 20JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 and v3.011 SUPERSEDES: NA SYMPTOM: When printing a job from QuarkXpress 3.0 or 3.1, the printer ready light blinks and blinks as if it is receiving the print job data, but nothing prints out (not even a PostScript error page). The job is removed from the queue because NetWare thinks that the job has printed correctly. The PostScript printer (such as HP IIIsi, QMS, NEC SilentWriter, Apple LaserWriter IINT) is configured as a PSERVER printer attached via the parallel or serial port. ISSUE/PROBLEM When graphics in the QuarkXpress print job are sent as "binary postscript" data over a non-AppleTalk channel (such as a non-binary channel), the binary control characters which represent the graphics are interpreted as printer control characters (0x14 = "request printer status," 0x4 = "end of job") and interfere with the printing of the job. SOLUTION Because Binary PostScript is supported over an AppleTalk channel (binary capable channel), one option would be to reconfigure the PostScript printer as an AppleTalk printer attached via LocalTalk or EtherTalk cabling. Otherwise, users will need to complete the following: For QuarkXpress 3.1 users, 1. The "!Son of Bob" XTension is needed (see below for more information on how to obtain this file). This file is an application extension and needs to be copied into the same folder where the QuarkXpress 3.1 application is located. 2. Then select the "Send ASCII PostScript" option from the File Menu.For QuarkXpress 3.0 users, the FeaturesPlus XTension is needed (FeaturesPlus is part of a package called Freebies XTension). This file is also an application extension and needs to be copied into the same folder where the QuarkXpress 3.0 application is located. To select ASCII versus binary postscript printing, do the following steps before opening a document: 1. Select the "Preferences" option from the "Edit" Menu. 2. Select the "Miscellaneous" option. 3. There will be an option for PostScript with two options available: - Binary - ASCII 4. Select the "ASCII" option. Please note that printing with ASCII PostScript is slower than printing with Binary PostScript. The Xtension files are available from the following: ■ Quark Technical Support (303/894-8899) or the following online services: ■ CompuServe:GO DTPFORUMLibrary 5 (Mac DTP Utilities) ■ America On LineKeyword> QuarkQuark, Inc. /Quark Downloads ■ XTensions Library Applelink Software Samples Third Party Demo /Updates Software Updates Quark FYI: New Features of the Apple LaserWriter IIg Printer FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: New Features of the Apple LaserWriter IIg Printer DOCUMENT ID#: FYI.W.0182 DATE: 20JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0X SUPERSEDES: NA SYMPTOM: NA ISSUE/PROBLEM What are the notable features of the new Apple LaserWriter IIg Printer? SOLUTION The LaserWriter IIg printer from Apple Computer is a PostScript laser printer with PhotoGrade and PostScript Level 2 features and also has the following notable characteristics: 1. When using the EtherTalk port of the LaserWriter IIg, the IIg can only be a Phase 2 EtherTalk device. Its EtherTalk port does not support Phase 1. 2. The LaserWriter IIg automatically chooses the Appletalk default zone at the nearest router. To set the Appletalk zone differently, download PostScript code to the printer. The default zone can be set persistently by this PostScript code: serverdict begin 0 exitserver (%EtherTalk%) <</EtherTalkZone (YourZoneHere)>> setdevparams Here is an example: serverdict begin 0 exitserver (%EtherTalk%) <</EtherTalkZone (Mac Zone)>> setdevparams 3. The LaserWriter IIg has a feature called "All Ports Active" which allows all three of the printer ports (LocalTalk, EtherTalk and RS232C ports) to be connected simultaneously and allows the IIg to switch between all three ports. Arbitration logic controls the activity of the ports. 4. The LaserWriter IIg supports HP PCL 4+ (equivalent to the LaserJet IIP) but does not have the ability to auto-sense the type of job (PostScript verses PCL) and cannot auto-switch between emulation modes (like the QMS ESP printers can). The IIg can be switched into/out of HP PCL mode either by sending it a PostScript program or by changing the switch settings and restarting the printer. 5. Apple recommends using the LaserWriter Utility 7.1 to rename the LaserWriter IIg instead of using the NAMER program. The Apple LaserWriter IIg also supports the following: ■ PostScript Level 2 ■ PhotoGrade - 65 levels of gray (versus 33 levels of gray on a LaserWriter IINTX) ■ FinePrint - smoothes jagged edges even at 300 dpi- Uses a 68030 CPU running at 25 MHz (versus 68020 CPU running at 16 MHz on a IINTX) and the IIg's clock speed is 55% faster than a IINTX. Ships with 5 MB RAM, supports maximum of 32 MB RAM ■ Burst mode RAM (transfers large amounts of data faster) and Data Cache. FYI: Compatibility Concerns between DataClub and SCSI Director Formatting Software FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Compatibility Concerns between DataClub and SCSI Director Formatting Software DOCUMENT ID#: FYI.W.0181 DATE: 20JUL92 PRODUCT: DataClub PRODUCT VERSION: v2.0 SUPERSEDES: NA SYMPTOM: The hard drive is unavailable for DataClub use. ISSUE/PROBLEM DataClub can not use removable media as storage for the virtual server. The SCSI Director formatting software defaults to a Finder eject feature that makes a nonejectable drive look ejectable to the Finder. This confuses DataClub. SOLUTION In the formatting software, disable the Finder eject feature. This can be done in the Control Panel device, or the formatting application without formatting the drive. FYI: Compatibility Concerns between DataClub and AppleTalk Remote FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Compatibility Concerns between DataClub and AppleTalk Remote DOCUMENT ID#: FYI.W.0180 DATE: 20JUL92 PRODUCT: DataClub PRODUCT VERSION: 2.0 SUPERSEDES: NA SYMPTOM: The user sees difficulty accessing files in DataClub on a LAN into which the user is dialing. ISSUE/PROBLEM DataClub does a lot of updating and talking to its own members especially when they come online. The remote machine is trying to communicate across the phone lines and becomes bogged down with network traffic. SOLUTION Turn off DataClub on the remote machine and access DataClub as an AppleShare Client. One of the DataClub machines in the LAN should have the gateway feature enabled and a separate machine should be the host for AppleTalk Remote. This will reduce the network traffic and allow the user dialing into the LAN to have a more stable connection. FYI: Compatibility Concerns between DataClub and Now Utilities Start-Up Manager FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Compatibility Concerns between DataClub and Now Utilities Start-Up Manager DOCUMENT ID#: FYI.W.0179 DATE: 20JUL92 PRODUCT: DataClub PRODUCT VERSION: 2.0 SUPERSEDES: NA SYMPTOM: Users will see erratic crashes at startup, or a strange colored background. ISSUE/PROBLEM The feature in the Startup Manager called "Show Invisible extensions" conflicts over the DataClub extension in the background operations of the Macintosh. SOLUTION Disable the "Show Invisible Extensions" in the Startup Manager portion of the Control Panel. FYI: Compatibility Concerns between DataClub and Retrospect FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Compatibility Concerns between DataClub and Retrospect DOCUMENT ID#: FYI.W.0178 DATE: 20JUL92 PRODUCT: DataClub PRODUCT VERSION: 2.0 SUPERSEDES: NA SYMPTOM: Users see the DataClub volume grayed out when using Retrospect backup software. There is also a problem when a incremental backup from within Retrospect is chosen. A full backup will be performed instead. ISSUE/PROBLEM DataClub is a more dynamic volume than a standard hard drive, such as its creation dates and sizes change. This confuses the Retrospect archive which assumes a more static structure. SOLUTION To perform an incremental backup, ensure that the backup program gets and uses the last backup date on the files, folders, and volume. To resolve the problem with DataClub volumes being grayed out, perform the backup from the machine where the root of DataClub is located. FYI: Compatibility Concerns between DataClub and Folder Bolt v.1.02c FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Compatibility Concerns between DataClub and Folder Bolt v.1.02c DOCUMENT ID#: FYI.W.0177 DATE: 20JUL92 PRODUCT: DataClub PRODUCT VERSION: 2.0 SUPERSEDES: NA SYMPTOM: Information stored in DataClub on a Macintosh with Folder Bolt becomes 0K in size and is unavailable. ISSUE/PROBLEM Folder Bolt creates its own hidden folder that overwrites the DataClub hidden folder where DataClub information is stored. The files can only be retrieved through an unerasing utility or restored from backup. SOLUTION The latest version of Folder Bolt (1.02c Plus) corrects this problem. Kent Marsh Inc. will provide the upgrade. FYI: Macintosh Login Name Limit FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh Login Name Limit DOCUMENT ID#: FYI.W.0176 DATE: 20JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: SYMPTOM: When logging into the NetWare for Macintosh server with a user name of more than 31 characters, an error is generated: "You have entered more characters than the maximum number allowed." ISSUE/PROBLEM When creating users through SYSCON be aware, there is a 31 character limit on a user name on the Macintosh system. SOLUTION Limit the login name for Macintosh users to 31 characters. FYI: DaynaPort driver Hangs the Macintosh FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DaynaPort driver Hangs the Macintosh DOCUMENT ID#: FYI.W.0175 DATE: 20JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: Every time the Macintosh prints or copies a file to the server (any server, so long as it is a phase II EtherTalk server) the Macintosh hangs. ISSUE/PROBLEM This is a known problem with early DaynaPort drivers. According to Dayna's Technical Support, drivers before 7.12 are known to have this trouble. SOLUTION Dayna has updated drivers on their Bulletin Board System (BBS) that fix problems like this. Dayna's BBS number is 801-535-4205. The file name is DP722. File DP722 contains the latest v7.22 drivers and installers for all the Dayna Macintosh Ethernet interface cards. FYI: AFP and the NOMULTIPLE Option FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AFP and the NOMULTIPLE Option DOCUMENT ID#: FYI.W.0174 DATE: 20JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: The rights for the user on the NetWare for Macintosh server become very unpredictable. Example: A user that seems to have all rights at the root of the volume may not be able to write a file to the volume. ISSUE/PROBLEM When loading AFP with the NOMULTIPLE option, the NetWare security system (for the Macintosh clients) becomes very complicated. The "NOMULTIPLE" option is used to make the NetWare Server use AppleShare rights instead of NetWare rights. If rights are then manipulated with a NetWare utility when NOMULTIPLE is loaded, the rights will become corrupt. When the "NOMULTIPLE" option is used, rights should only be manipulated through the AppleShare utilities on the Macintosh workstation. Because no one-to-one correspondence exists between AppleShare rights and NetWare rights when the wrong utility is used, the file server's rights become corrupt. SOLUTION Do not use the NOMULTIPLE option with the AFP.NLM unless the following is known: ■ The complete NetWare's security configuration ■ How to assign AppleShare security so the two different systems do not conflict. For a description of this option, please read the NetWare for Macintosh Installation manual v3.0, page 110. FYI: Morie Screen Saver and DataClub FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Morie Screen Saver and DataClub DOCUMENT ID#: FYI.W.0173 DATE: 17JUL92 PRODUCT: DataClub PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: When using DataClub and the Morie Screen Saver together, the Macintosh screen freezes. ISSUE/PROBLEM The Morie Screen Saver and DataClub conflict with each other. SOLUTION Remove the Morie Screen Saver to resolve this issue. Other screen savers that work with DataClub include AfterDark and Pyro. FYI: Radius Accelerator in a Macintosh Plus and DataClub FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Radius Accelerator in a Macintosh Plus and DataClub DOCUMENT ID#: FYI.W.0172 DATE: 17JUL92 PRODUCT: DataClub PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: Cannot see any information in DataClub when accessing the Control Panel. ISSUE/PROBLEM When installing DataClub on a Macintosh Plus with a Radius Accelerator board, DataClub installs its own version of AppleTalk. SOLUTION Delete the DataClub version of Appletalk, and use the Radius version, called Radiusware, in the System Folder. This problem only occurs with the Macintosh Plus machines. FYI: DataClub and TOPs 3.0 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DataClub and TOPs 3.0 DOCUMENT ID#: FYI.W.0171 DATE: 17JUL92 PRODUCT: DataClub PRODUCT VERSION: 2.0 SUPERSEDES: NA SYMPTOM: Can't get needed resource error is returned when accessing DataClub in the Control Panel. ISSUE/PROBLEM The TOPs program has a patch that conflicts with the DataClub Control Panel file. SOLUTION Remove TOPs, or execute DataClub and ignore the error message. Be aware there will be no access to the Control Panel if the error message is ignored and TOPs is still installed. FYI: DataClub and Quark Express 3.0 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DataClub and Quark Express 3.0 DOCUMENT ID#: FYI.W.0170 DATE: 17JUL92 PRODUCT: DataClub PRODUCT VERSION: Any SUPERSEDES: NA SYMPTOM: The Quark Express v3.0 Tiff file looses links when saved on the DataClub server. This will cause pieces of the Tiff file to be missing. ISSUE/PROBLEM DataClub will search for the link files in the directory where the Quark file is saved. If the links are stored elsewhere they will not be found. SOLUTION Store all links in the same DataClub directory as where the Quark Tiff file is saved. FYI: System Picker with DataClub FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: System Picker with DataClub DOCUMENT ID#: FYI.W.0169 DATE: 17JUL92 PRODUCT: DataClub PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: "Unimplemented trap error" is received on the Macintosh when booting with System Picker. System Picker allows a Macintosh to boot to either System 6.x or System 7.x. ISSUE/PROBLEM DataClub must rebuild its indexes when the Macintosh boots. When DataClub is installed for both the System 6.x and System 7.x on the same Macintosh, only the System selected will be updated, so corruption can occur. SOLUTION Do not use System Picker with DataClub. FYI: DataClub and Partitioning Software FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DataClub and Partitioning Software DOCUMENT ID#: FYI.W.0168 DATE: 17JUL92 PRODUCT: DataClub PRODUCT VERSION: 2.0 SUPERSEDES: NA SYMPTOM: Disk or partition does not show up in the Control Panel under DataClub or a message "Please restart to add the newly checked disk" is received. ISSUE/PROBLEM The Macintosh hard drive was partitioned with Diversified or Mirror Software. SOLUTION When partitioning the drive with Diversified or Mirror Software either take the partitions off or reformat with another formatting software like Silverlining. When using Soft Partition Software, be sure to load it before DataClub so that it can recognize the partitions. FYI: Cisco Routers on Ethernet and Token-Ring FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Cisco Routers on Ethernet and Token-Ring DOCUMENT ID#: FYI.W.0167 DATE: 17JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.x, 3.x SUPERSEDES: NA SYMPTOM: Customer was using Cisco's multi-protocol router, ATP-Plus, to link a NetWare v2.2 server (with the v2.2 Macintosh VAPs loaded) on Ethernet to a Token-Ring network, which had several NetWare v2.15c, v3.1 and v3.11 servers. The Macintosh machines, which were connected to the Ethernet network, would randomly lose their connection to the file servers, which were on Token-Ring. Through the Chooser, users would sometimes see all of the file servers connected on the Ring. Other times, the servers would pop in and out of the Chooser. ISSUE/PROBLEM Everything seemed to be working fine for the Macintosh machines until more AppleTalk traffic was generated by adding about 20 more Macintosh machines to the Ethernet network. Cisco Technical Support was contacted and was aware of this problem of routing AppleTalk traffic from Ethernet to Token-Ring, where the Routing Tables would eventually receive garbage across the net and become corrupt. SOLUTION The ROM revision level GS3-BFX v8.2 Release 5, Bootstrap v4.3 Release 3 does indeed have problems as indicated above. Users experiencing similar problems should contact Cisco for a ROM level upgrade to revision level GS3-BFX v8.3 Release 1, Bootstrap v4.4, Release 1. FYI: APSVAP and AQSVAP FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: APSVAP and AQSVAP DOCUMENT ID#: FYI.W.0166 DATE: 16JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.x SUPERSEDES: NA SYMPTOM: The NetWare for Macintosh queues stop processing jobs and the following errors appear at the console: APSVAP:Unable to service next job. Error #1Printer <Printer Name> stopping due to an unexpected error. AQSVAP:Unable to service next job. Error #1 or 6. ISSUE/PROBLEM The problem is that the value-added processes (VAPs) are being logged off of the file server. This can be caused by the bindery being closed. The bindery will sometimes be closed while executing certain backup programs. SOLUTION Reboot the server after executing the backup. Novell and Dayna are currently investigating a possible retry in the value-added processes (VAPs). FYI: NetWare v2.2 Router - "Login Failure - error code 251" FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare v2.2 Router - "Login Failure - error code 251" DOCUMENT ID#: FYI.W.0164 DATE: 13JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: The following error message keeps scrolling by on the NetWare v2.2 Router console, "Login Failure - error code 251". ISSUE/PROBLEM The bindery information used for NetWare for Macintosh printing has become corrupt. SOLUTION Execute the MACDEL program. This will clean out all corrupt NetWare for Macintosh printing information in the bindery. After this, reconfigure the NetWare for Macintosh print services. MACDEL can be obtained through the NSEPRO and on NetWire or NetWare Express. FYI: Mounting the Wrong Volume FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Mounting the Wrong Volume DOCUMENT ID#: FYI.W.0165 DATE: 10JUL92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.01 and 3.011 SUPERSEDES: NA SYMPTOM: When mounting a volume on the server from the Macintosh client, either the volume does not mount, or another volume mounts instead of the one selected. ISSUE/PROBLEM This has been found to be a problem with NetWare for Macintosh servers running v3.01 NetWare for Macintosh with the AFPFIX4 patch to resolve a Farallon PhoneNet Talk problem, or when using v3.011 NetWare for Macintosh. When there are multiple volumes on the server and the characters in the volume name match the characters used in the server name, the server becomes confused and will mount the wrong volume. Example: If the NetWare server name is NET_Server and there are three volumes (SYS, VOL1, and NET), when mounting the NET volume, because the server name also begins with the characters N E T, the server may be confused and mount another volume instead. SOLUTION There are many possible workarounds to this problem. 1. Rename the volume from within the INSTALL program on the NetWare v3.11 server to a name that does not use the same characters that are used in the server's name. 2. A hidden file called VOLNAMES.AFP is in SYS:SYSTEM. VOLNAMES.AFP is where the names of the volumes as they will appear to the Macintosh client are held. By default, this file should only contain a line for the SYS volume that will look something like: SYS=NET_SERVER.SYSReflag this file so it can be edited and add a line that will remap the volume in question. For example: SYS=NET_SERVER.SYSNET=NET_SERVER.NET This command will force the server to look at all the characters in the server name and to find the correct volume at mount time. FYI: Unable to LOAD AFP, change net numbers FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Unable to LOAD AFP, change net numbers DOCUMENT ID#: FYI.W.0162 DATE: 22JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When trying to LOAD AFP it fails with the error "Can't open VOLICON file". ISSUE/PROBLEM Many files in SYS:SYSTEM hold configuration information for NetWare for Macintosh. These files are flagged correctly when they are installed, but if they are reflagged with ROS (Read Only, Shareable), they will not be updated with new information when a configuration parameter is changed. SOLUTION If this problem occurs, make sure the file in question is flagged with RW (Read, Write) attributes. FYI: Printing with PageMaker 4.2 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printing with PageMaker 4.2 DOCUMENT ID#: FYI.W.0161 DATE: 22JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When printing to a queue with PageMaker v4.2 there are errors generated like: [Error: undefined; Offending Command: AldusDict2] or ATPS: open dictionary file: no such file or directory. ISSUE/PROBLEM This problem can occur when using PageMaker v4.2 to print to a server that has never spooled jobs from an earlier version of PageMaker. When the PageMaker v4.2 jobs are submitted to a printer, they fail to print and the above PostScript exception errors are returned. This is because Aldus changed the PageMaker AldusPrep dictionary to parse its version and revision information incorrectly when it is downloaded to the spooler. As a result, ATPS saves the dictionary with an incorrect name and ATPS is unable to access the file when it is time for the job to be printed. SOLUTION If this problem occurs, go into the ATPS directory on the server (the default is SYS:SYSTEM/ATPS) and rename a file named either "ALD00.PRS" or "AL00.PRS" to "ALD20955.PRS". This will correct the problem permanently for all ATPS spoolers on this server, unless the file is later deleted or renamed, or the ATPS directory is changed. FYI: Unreleased resources FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Unreleased resources DOCUMENT ID#: FYI.W.0160 DATE: 22JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0, v3.01 SUPERSEDES: NA SYMPTOM: When unloading the ATPS NLM there is a warning message about unreleased resources. ISSUE/PROBLEM When ATPS is unloaded, it may not release some of its resources, especially if printing is in progress. Instead, the release is performed by the operating system, which prints messages on the console. SOLUTION Since the operating system will release these resources anyway, ignore these messages. FYI: Unable to Retrieve Font List FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Unable to Retrieve Font List DOCUMENT ID#: FYI.W.0159 DATE: 22JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0, v3.01 SUPERSEDES: NA SYMPTOM: When setting up a queue to a printer with a large font list or attached hard drive with a large font list, the queue will not initialize. ISSUE/PROBLEM When the ATPS NLM loads it queries the printer for the fonts it is using to build a font list. If the printer has many fonts and a PostScript error is generated while the font list is being built, the font list may not be complete, or may cause the queue not to advertise itself. SOLUTION To solve this problem upgrade to v3.011 NetWare for Macintosh. FYI: Zones not displayed correctly FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Zones not displayed correctly DOCUMENT ID#: FYI.W.0158 DATE: 22JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0, v3.01 SUPERSEDES: NA SYMPTOM: After setting up the zones in the ATZONES.CFG file and loading all the NetWare for Macintosh NLMs, when viewing the zone names from the Macintosh's Chooser, the first character of the zone name is dropped. ISSUE/PROBLEM There is a known problem where if a nonalphanumeric character (such as spaces or punctuation) is used it will be dropped. For example, if the zone ".Tone Zone" is used, only "Tone Zone" will be read as the zone name. SOLUTION There are a few possible solutions. ■ One would be to not use nonalphanumeric characters in the zone name. ■ A second solution would be to upgrade to v3.011 of NetWare for Macintosh. Version 3.011 of NetWare for Macintosh solves this problem. FYI: More Than One Alias per Server Volume Using VOLNAMES.AFP. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: More Than One Alias per Server Volume Using VOLNAMES.AFP. DOCUMENT ID#: FYI.W.0163 DATE: 18JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0x SUPERSEDES: NA SYMPTOM: When configuring the VOLNAMES.AFP file to contain two aliases for a volume on the server, only the first alias shows up in the Chooser on the Macintosh. ISSUE/PROBLEM The VOLNAMES.AFP file is used to setup aliases to volume names on NetWare v3.11 file servers. An example of this file might look like this: SYS=MyServer.sysVOL1=MacintoshVolume These alias names will show up in the Chooser as volume names when logging into a NetWare v3.11 server from a Macintosh. If more that one alias is listed for a particular volume (see example below), only the first alias will show up in the Chooser. Any other aliases for the same volume will be ignored. SYS=MyServer.sysSYS=YourServer.sys <-- This entry will be ignored. VOL1=MacintoshVolume SOLUTION Configure the VOLNAMES.AFP file with only one alias per volume on a NetWare v3.11 server. FYI: Maximum Length of Message using the NetWare DA Message Module FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Maximum Length of Message using the NetWare DA Message Module DOCUMENT ID#: FYI.W.0157 DATE: 18JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: all SUPERSEDES: NA SYMPTOM: The maximum length of a message sent using the NetWare DA Message Module is inconsistent and can vary anywhere from 32 to 39 characters. There seems to be no consistent pattern as to when the maximum length will be 32 verses 35 verses 39. The maximum length of a message which is sent from the File Server console using the BROADCAST command and received on a Macintosh machine using the NetWare DA Message Module appears to be 57 characters even though a DOS workstation can only receive a message of maximum length of 55 characters. The maximum length of a message which is sent from a DOS PC using the SEND command and received on a Macintosh machine using the NetWare DA Message Module appears to be 43 characters even though a DOS workstation can only receive a message of maximum length of 40 characters. ISSUE/PROBLEM A problem with the NetWare DA Message Module exist and there seems to be no consistent pattern as to what the maximum length will be. SOLUTION Currently, there is no solution to this problem. FYI: Printing From a Windows v3.1 Client to NetWare Queue Results In Postscript Error Pages FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printing From a Windows v3.1 Client to NetWare Queue Results In Postscript Error Pages DOCUMENT ID#: FYI.W.0156 DATE: 18JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: all SUPERSEDES: NA SYMPTOM: Printing from a Windows v3.1 client to a NetWare queue results in PostScript Error Pages (such as Offending Command), but the same workstation can print without any problems to the same NetWare queue if printing a PostScript job from non-Windows programs. ISSUE/PROBLEM This is similar to the problem in Windows 3.0 when printing to LPT1 port versus LPT1.OS2 port (For example: Windows tries to write directly to the BIOS, bypassing standard DOS calls) resulting in PostScript errors. SOLUTION When printing from a Windows v3.1 client to a NetWare queue, make sure that "Fast Printing Direct to Port" is turned off in the Control PanelPrintersConnect menu. FYI: NetWare for Macintosh and HPIIIsi FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare for Macintosh and HPIIIsi DOCUMENT ID#: FYI.W.0155 DATE: 18JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: How is printing with NetWare for Macintosh and a HPIIIsi printer configured? ISSUE/PROBLEM Users have expressed great interest in having Macintosh and PC machines sending output to the HPIIIsi connected on Ethernet or Token Ring and having the HPIIIsi switch between PostScript and PCL page description languages. Many variables exist in setting up this configuration. The following is a brief introduction to the HPIIIsi, and the solution section discusses how mode switching works and how to configure the components in order to work together. The HPIIIsi is a 17 ppm laser printer that has options for serial/parallel, LocalTalk, Token-Ring, or Ethernet interfaces. The Ethernet and Token-Ring interfaces have configurations for Novell and 3Com/LanMan networks. The 3Com/LanMan interfaces will not be discussed in this FYI. SOLUTION In February, 1992, HP began shipping an EtherTalk network interface card for the HPIIIsi. The card will support either AppleTalk Phase I or Phase II protocols. It is important to note that the ability to switch between PostScript and PCL can not be done with the LocalTalk, or EtherTalk card. At this time, PCL over PAP is not supported by the HPIIIsi. The serial/parallel and Novell interfaces can switch modes, using print jobs set up with the NetWare PRINTCON utility. In order to have the mode switching feature work automatically, the HPIIIsi needs to be configured to default to PostScript, and have system switching mode enabled. NOTE: There is a bug within the HPIIIsi's firmware that intermittently fails to update the LCD display with the string PS Ready after the printer has switched to PCL mode. This problem is cosmetic and should be resolved by HP sometime in the future. The ability to switch modes comes from defining a print job with the PRINTCON utility. PDF files for the HPIIIsi are shipped with NetWare v3.11 and copied to SYS:\PUBLIC during installation. PDF files also ship with the Network Printer interface for Novell kit, but they are an older date than what comes with the 3.11 NetWare operating system. The "HP LaserJet IIIsiPCL" device needs to be selected in PRINTCON. This device has modes set up for fonts, paper size, etc. Each mode contains the commands to tell the HPIIIsi to switch to PCL. At the end of each job, the Reinitialize mode is sent, which, in its default, contains the command to exit the current language that the printer is executing (in this case, PCL). In short, the HPIIIsi defaults to PostScript mode, the PRINTCON job places the commands to switch to PCL into the queue, then the actual data from the PC machine, and finally places the command to exit PCL mode at the end of the job. Most users have the impression that the sending machine has to tell the HPIIIsi which mode to print, this is untrue. To summarize, a print job configured to use PCL will contain the commands to enter PCL mode at the beginning of the job and will have the command to exit PCL mode at the end of the job. The HPIIIsi has the ability to be its own print server (a term HP calls queue server mode) or can be serviced by the Novell print server, including RPRINTER (it can even run the RPRINTER software from its Novell Interface card). Either way will work, according to HP, queue server mode is faster. The EtherTalk interface does not support the RPRINTER or QUEUE SERVER modes. Other issues to note, the Adobe PostScript kit and the Duplex printing module are options. To use the duplexing option from a Macintosh machine, if the HPIIIsi has the duplexing unit installed, the HPIIIsi rDev is needed. The HPIIIsi rDev is NOT included with the Network Printer Interface for Novell networks. If a user needs the rDev they can contact their HP dealer, HP Sales Rep, or the HP Personal Peripherals Assist line at (208)3232551. The only other issue that is undetermined is printing from Windows using PCL when attaching to the NetWare queue through the Printers utility of Windows. At this time, this configuration has not been fully tested, but appears to function properly. Configurations: HPIIIsi: (configuration information obtained by taking the printer OFFLINE and holding down the TEST key) Configuration menu: SYS = POSTSCRIPT SYS SWITCH = ON AUTO CONT, RET, START PAGE, JAM RECOVER, JOB OFFSET, PRT PS ERRS = all don't care PRINTDEF: Import HP3SIPCL.PDF from SYS:\PUBLIC. If having problems switching back to PostScript, verify that the Reinitialize function contains the "Universal Exit Language" command as its only entry. PRINTCON: Number of Copies: don't care Form Name: don't care File contents: don't care Print Banner: NO Tab size: don't care Name: Suppress Form Feed: YES Banner name: Notify When Done: don't care Enable Timeout: NO Local Printer: don't care Timeout Count: Auto Endcap: YES File Server: as configured Print Queue: as configured Print Server: as configured Device: HP LaserJet IIIsiPCL Mode: any other than ReInitialize ATPS.CFG: o queuename wb f HPLASER l FYI: VAP Limitation FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: VAP Limitation DOCUMENT ID#: FYI.W.0154 DATE: 18JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: When many NetWare routers are on a network all running the Macintosh VAPs, they all must attach to a server on the network the same as a DOS workstation. With all the Macintosh VAPs loaded on a router, eight connections will be taken on the server for this attachment. If all the NetWare routers attach to the same server, there will be no connections left for users to login with. ISSUE/PROBLEM This is a problem with the VAP and router architecture. SOLUTION A few workarounds to this problem are as follows: If the VAPs are on the NetWare servers and not the routers, these attachments are made internally to the server so this would solve the problem. Also, segmenting the network so only a few routers can attach to the same server would help. This would allow a limited number of connections to be used for the Macintosh VAPs. A third solution would be to include a v3.x NetWare server on the network. NetWare v3.x is not impacted by these attachments as a NetWare v2.x server is. As a fourth possible solution, upgrading to v3.x NetWare for Macintosh would also solve the problem, but it must be loaded on a v3.11 NetWare file server. FYI: DCA IrmaTrack TokenTalk Interface Cards FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DCA IrmaTrack TokenTalk Interface Cards DOCUMENT ID#: FYI.W.0152 DATE: 17JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: In certain Macintosh machines, specifically the Macintosh IICI and Macintosh IICX, if a user selected the TokenTalk driver for the DCA IrmaTrack TokenTalk cards through the Network portion of the Control Panel, these particular Macintosh machines would automatically change back to the BuiltIn driver, rather than stay selected on TokenTalk. ISSUE/PROBLEM This is a well known problem with Revision A of DCA TokenTalk interface cards for the Macintosh II series. SOLUTION DCA has tested and released Revision B of these network interface cards for the Macintosh that will fix this problem of switching to the BuiltIn driver. Contact DCA for the new revision. FYI: Using the APPLETLK.NLM with the i flag FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Using the APPLETLK.NLM with the i flag DOCUMENT ID#: FYI.W.0153 DATE: 12JUN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.011 SUPERSEDES: NA SYMPTOM: Neither the AFP.NLM, ATPS.NLM nor ATLKSNMP.NLM can be successfully loaded. When loading AFP.NLM, the following error message is returned: mm/dd/yy (time) 0.0.0 AFP MODULE: Unable to open server listening socket. Error 1 When loading ATPS.NLM, the following error message is returned: mm/dd/yy (time) 0.0.0 ATPS: Can't open SYS:SYSTEM\ATPS.CFG, unloading When loading ATLKSNMP.NLM the following error message is returned: mm/dd/yy (time) Loader cannot find public symbol: xxx (This message repeats six times each with it's own symbol) ISSUE/PROBLEM If the APPLETLK.NLM is loaded with the i flag, no internal network is created. In this event, none of the AppleTalk NLMs which reside on the internal AppleTalk network of the file server (like AFP.NLM, ATPS.NLM and ATKLSNMP.NLM) can be loaded. SOLUTION 1. LOAD APPLETLK.NLM with the appropriate network parameters (net number and zone name). 2. Do not use the i flag if anything more than routing is required from the server. The i flag is documented on pages 102 and 122 of the AppleTalk Support Package manual. 3. Please read these pages for a brief description of the i flag. In short, this flag should be used when the NetWare for Macintosh server is to act as a TRUE AppleTalk router only. 4. If file, print, or SNMP services are required, do not use the i flag. FYI: AFPFIX2 & 6 Conflict FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AFPFIX2 & 6 Conflict DOCUMENT ID#: FYI.W.0151 DATE: 26MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When AFPFIX6 is loaded on the server to resolve problems where the Access Control right is needed to create a folder, it doesn't resolve the problem. ISSUE/PROBLEM If you have AFPFIX2 loaded (this fixes the bindery closure problem on System 7 Macs) and AFPFIX6 loaded (this fixes the Access Control right issues on System 7 Macintosh) on the same server, AFPFIX6 will not work. SOLUTION The only workaround for now is to take off AFPFIX2 to get AFPFIX6 to work. FYI: Rename Inhibit Flag FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Rename Inhibit Flag DOCUMENT ID#: FYI.W.0150 DATE: 26MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0, v3.01, and v3.011 SUPERSEDES: NA SYMPTOM: If a Macintosh user tries to move Macintosh application while it is in use the Macintosh will hang and eventually all users will be disconnected from the file server and the server must be rebooted. ISSUE/PROBLEM There is a known problem described in the NetWare for Macintosh v3.01 readme where if a user moves a Macintosh application on the server while the application is in use it will hang the Macintosh and will corrupt the volume directory structure. The solution described is to not perform this operation. SOLUTION Another alternative would be to flag the Macintosh applications on the server with the Rename Inhibit (RI) flag. for example: flag <mac application> RI This will not allow users to move the file so instead of the Macintosh hanging and the server's volume becoming corrupt, the user will get an error message and the application will not be moved. FYI: NetWare UAM and non-English Macintosh OS FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare UAM and non-English Macintosh OS DOCUMENT ID#: FYI.W.0149 DATE: 26MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0, 3.01, and 3.011 SUPERSEDES: NA SYMPTOM: When the NetWare UAM is installed in a non-English Macintosh OS the user isn't prompted to use the clear text or NetWare Encrypt option. ISSUE/PROBLEM To install the NetWare UAM, the user must create a folder under the System folder called AppleShare Folder and copy the NetWare UAM file there. The problem is the language the Macintosh OS is using doesn't look in the AppleShare Folder, but a folder with this name in the native language. SOLUTION To resolve this problem a sophisticated user can use ResEdit to alter the name "AppleShare Folder" to be in the native language. This is done by editing the AppleShare file (usually in the Extensions folder in the System folder for System 7) in ResEdit and choosing the "STR " resource. Then choose "-4082" and copy the string between the colons to the name of the AppleShare Folder under the System folder. This will allow the OS to look in the correct place for the UAM. Users should be warned that using ResEdit to change system resources can cause corruption. Make sure backups are available before any changes with a resource editor are made. FYI: Bullet Characters in Printer's Name FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Bullet Characters in Printer's Name DOCUMENT ID#: FYI.W.0148 DATE: 26MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2, v3.0, and v3.01 SUPERSEDES: NA SYMPTOM: The NetWare for Macintosh queue can not attach to the printer. ISSUE/PROBLEM When viewing the printer through the Chooser on the Macintosh, the text in the name of the printer looks normal. When viewing the printer using ATCON or Interpol, three bullet characters lead the rest of the text in the name of the printer. The NAMER program by Apple has problems which causes naming inconsistencies. Usually a space character is inserted at the end of the printer name. This time the characters were not spaces, and were inserted in the front of the printer's name. These characters were interpreted by ATCON as bullet characters (unknown). SOLUTION Use the NAMER to re-name the printer. This may take several tries. In this case, the printer had to be renamed by the Namer program three times. Each time a single bullet character was removed from the printer's name. Check your network management application (ATCON, Interpol, etc...) to verify the name of your printer. FYI: NFS and ATPS FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NFS and ATPS DOCUMENT ID#: FYI.W.0147 DATE: 26MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: The NFS queues will not attach to the NetWare for Macintosh queues created in ATPS. ISSUE/PROBLEM NFS can only attach to NetWare print queues (including ATPS queues) which "live" on the server which hosts the NFS services. In other words, NFS cannot attach to ATPS queues which live on remote servers. SOLUTION A work around for this problem is to simply use the routing functionality and attach the local queue to a printer that is located on a LocalTalk segment of another server. This will put the ATPS queue on the server that has NFS services. FYI: ATNODES.DAT FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATNODES.DAT DOCUMENT ID#: FYI.W.0146 DATE: 26MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: The error "ATALK: updat param-node file SYS:SYSTEM/ATNODES.DAT create failed (Err=6)" is generated at the system console. ISSUE/PROBLEM The ATNODES.DAT file is used to keep AppleTalk network information. If this file is flagged incorrectly, network information will not be updated as it becomes available. If this file isn't updated, the NetWare server's AppleTalk router will not know about other AppleTalk routers on the network. This can cause routing problems. SOLUTION To resolve this problem flag the ATNODES.DAT file RW (Read Write). This file is in SYS:System on the file server. After this is complete, unbind and re-bind APPLETLK to the LAN driver so the AppleTalk network information will be updated properly. FYI: Printing to an ImageWriter FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printing to an ImageWriter DOCUMENT ID#: FYI.W.0145 DATE: 26MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 and 3.01 SUPERSEDES: NA SYMPTOM: Jobs will not print when sent to a queue for an ImageWriter on LocalTalk. ISSUE/PROBLEM When setting up a queue for an ImageWriter, the type of printer being used must be defined in the ATPS.CFG file with the -t option. For example, if the ATPS.CFG file looks like this: "LOCAL IMAGEWRITER:ZONE1" -o "IMAGEWRITER QUEUE" the jobs will not print. The correct entry in the ATPS file would look like this: "LOCAL IMAGEWRITER:ZONE1" -o "IMAGEWRITER QUEUE" -t ImageWriter SOLUTION Use the -t option when defining queues for ImageWriter printers. FYI: Connection Failure with Notify and Shiva's Dial-In system init. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Connection Failure with Notify and Shiva's Dial-In system init. DOCUMENT ID#: FYI.W.0144 DATE: 22MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: The Shiva Dial-In init (v3.6.6) and the NetWare Notify init(v2.11) are installed on a remote Macintosh workstation. When dialing into a Shiva NetModem/E from this remote Macintosh workstation to get onto the network, the connection fails and results in the error message "Cannot connect. Remote network failed to respond." ISSUE/PROBLEM The cause of this problem is not known. Note that this is only a problem with the Shiva NetModem/E not the regular Shiva NetModem. SOLUTION Currently, there is no solution to this problem. As a workaround: 1. Remove the Notify init from the Macintosh that is being used to dial in. 2. Dial into a regular NetModem instead of a NetModem/E. FYI: Some AppleShare Resources Were Not Installed at System Startup Time FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Some AppleShare Resources Were Not Installed at System Startup Time DOCUMENT ID#: FYI.W.0143 DATE: 22MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: When logging in, a user can select the AppleShare Icon in the Chooser and can also select the File Server Name from the list in the Chooser, but cannot log into the NetWare File Server and receives the error message "Some AppleShare resources were not installed at system startup time. Try restarting from an AppleShare workstation disk or reinstall the workstation software." ISSUE/PROBLEM The AppleShare workstation software was not correctly installed (e.g. the AppleShare icon was probably copied to the System Folder by copy-drag method). SOLUTION Re-boot the Macintosh from the Macintosh System Operating System Installer disk and run the Macintosh Operating System Installer program. Select the Customize button and select AppleShare Workstation Software (System 6.0.x Macs) or select File Sharing Software (System 7.x Macintosh) from the list of items to install. FYI: Changing the User Name in the 'Connect to the File Server' Login Screen FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Changing the User Name in the 'Connect to the File Server' Login Screen DOCUMENT ID#: FYI.W.0142 DATE: 22MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: When logging into the file server through the chooser, there is a name listed as the default user name. How can this be changed? ISSUE/PROBLEM The Login Name that appears in the 'Connect to the File Server' Login screen is saved by the Macintosh Operating System. In System 6.0.x Macintosh, the login name is taken from the 'User Name' specified in the Chooser window (right above the Appletalk-Active, Inactive option). In System 7.x Macintosh, the login name is specified in the Sharing Setup option from within the Control Panel. SOLUTION In System 6.0.x Macintosh, change the 'User Name' specified in the Chooser window. In System 7.x Macintosh, change the user name in the Control Panel, - Sharing Setup option. The name will be saved as soon as the Chooser window or the Sharing Setup window is closed. FYI: Emerald backup version 3.11EH FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Emerald backup version 3.11EH DOCUMENT ID#: FYI.W.0141 DATE: 22MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01, v3.0, and v2.2 SUPERSEDES: NA SYMPTOM: Macintosh files are not backed up in volumes which do contain the Macintosh name space. ISSUE/PROBLEM The new backup software for Emerald (version 3.11EH) only checks the SYS volume to determine if the Macintosh name space is supported or not. If there are volumes which support the name space, and the SYS volume does not support the MAC name space, Macintosh files will not be backed up correctly. Therefore, when these files are restored they will be corrupt. SOLUTION Emerald is aware of the problem, and is currently working on a solution. FYI: Running HyperCard on a NetWare server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Running HyperCard on a NetWare server DOCUMENT ID#: FYI.W.0140 DATE: 21MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2, v3.0, v3.01 SUPERSEDES: NA SYMPTOM: When switching between multiple open HyperCard stacks that are running on a NetWare server, the following error is returned on the Macintosh; "Can't open stack <pathname for stack>". ISSUE/PROBLEM One of the options in the 'Open Stack...' or 'New Stack...' dialog box is a check box that allows you to open the new or existing stack in its own window, leaving the current stack on the desktop. While only one stack can be active at one time, you merely need to click on a stack to activate it. When running two stacks on one Macintosh from a Novell server, however, switching back to the first stack, after opening up a second (in its own window), results in an error "Can't open stack <pathname for stack>". This error does not occur when running stacks from an AppleShare server or the Macintosh hard drive. The following versions of HyperCard were all found to have the same problem: v2.0, v2.0v2, v2.1. SOLUTION A workaround would be to only open one stack at a time (don't click on the "open stack in new window" check box). FYI: ATPS Print Queues and the NetWare DA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS Print Queues and the NetWare DA DOCUMENT ID#: FYI.W.0139 DATE: 14MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: An ATPS Print Queue name that includes a "(" , will cause the print queue to be grayed out and unavailable when viewed by the NetWare Desk Accessory. ISSUE/PROBLEM You cannot have a left parenthesis as a valid character in a print queue name and view it successfully in the NetWare Desk Accessory. The print queue will be grayed out (you will be unable to select it) and the name of the queue will be shown without the left parenthesis. The queue will initialize successfully and users will be able to print to it; but, you will be unable to monitor the print job status via the NetWare DA. This is a bug with the Print Queue Module of the NetWare DA and will be resolved in subsequent releases. SOLUTION Change the name of the AppleTalk Print Queue in the ATPS.CFG file to not include a left parenthesis. You should also delete the print queue that contains the left parenthesis in PCONSOLE. Unload and reload ATPS for the new AppleTalk print queue to initialize. FYI: Secure Console Command FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Secure Console Command DOCUMENT ID#: FYI.W.0138 DATE: 14MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When trying to install NetWare for Macintosh, the following message would result, no matter what path was specified (even SYS:SYSTEM) to copy over the NLM's: "File console is secure. Path specifiers are no longer allowed. Unable to find PINSTALL." ISSUE/PROBLEM In the AUTOEXEC.NCF file, there was the SECURE CONSOLE command, which allows the following security measures to be implemented on the file server: Prevents NLM's from being loaded from any directory other than SYS:SYSTEM Prevents keyboard entry into the OS debugger Prevents anyone other than a console operator from changing the date and time Removes DOS from the file server Without the console "secured", an intruder can create a NLM that can access or alter any information on the file server. These NLM's can change user account information and the bindery security level. In addition, a module can be loaded from a DOS partition, a diskette drive, or any directory on a NetWare volume, if the console has not been secured. The file server having been "secured" prevented the PINSTALL from successfully loading the NetWare for Macintosh software. What was needed was to "unsecure" the console and proceed with the installation process. SOLUTION There is not a command to "unsecure console". What needs to be done is to remove or remark the SECURE CONSOLE statement out of the AUTOEXEC.NCF file and reboot the file server with the console not secured. Then proceed with the product installation and reenter the SECURE CONSOLE command and reboot the file server. FYI: VAPs lock Router FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: VAPs lock Router DOCUMENT ID#: FYI.W.0136 DATE: 07MAY92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: When the Macintosh VAPs load on the external router, it hangs. ISSUE/PROBLEM On the Network, all the IPX devices were Econfiged and were using the Ethernet -11 frame type. This router's Ethernet card, the NE2000, was not Econfigured and was using the 802.3 frame type. SOLUTION To resolve this problem, Econfig the NE2000 LAN driver to change it to the Ethernet_II frame type. FYI: Slow Printing FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Slow Printing DOCUMENT ID#: FYI.W.0135 DATE: 30APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.011 SUPERSEDES: NA SYMPTOM: Printing to the NetWare Queue is much longer than printing directly to the printer. ISSUE/PROBLEM The 5.2 LaserWriter driver must have fonts downloaded one at a time. After v5.2, 6.x and 7.x LaserWriter drivers download fonts in 512 byte packets. This greatly enhances printing performance, especially when many fonts are used. Because ATPS must be compatible with 5.2, 6.x and 7.x LaserWriter drivers it also must download fonts to the printer one at a time. SOLUTION There is an undocumented and untested features of v3.11. ATPS that comes with NetWare for Macintosh v3.011. Using a "-r" option in the ATPS.CFG file when defining the queue with cause ATPS to use the 512 byte font downloaded and increase performance. This is used as follows: "LaserWriter: Zone 1 "-0" Queuename" -r No one printing to this queue can use the 5.2 (or below) LaserWriter driver. FYI: Using The Namer to change the name of a print queue. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Using The Namer to change the name of a print queue. DOCUMENT ID#: FYI.W.0134 DATE: 30APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: When using the Namer program to change the name of a LaserWriter, the names of the NetWare for Macintosh queues also appear when changing the name of one of the queues, the name of the printer that the queue is servicing disappears and the new name that was entered is now the name of the printer. ISSUE/PROBLEM The Namer utility views the queue names as if they were actual printers, so changing the name of the queue, sends out a request to change the name of the printer that is serviced by that queue. SOLUTION It is not recommended to change the name of queues, only actual printer names. FYI: NetWare Control Center and Changing Passwords to Less than the Minimum Length Required FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare Control Center and Changing Passwords to Less than the Minimum Length Required DOCUMENT ID#: FYI.W.0133 DATE: 29APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0x SUPERSEDES: NA SYMPTOM: Users on a v3.0 or v3.01 NetWare for Macintosh Server can change their password to a 'shorter' password than what is required by the 'Minimum Password Length' assigned in SYSCON (User Account Restrictions). This can be done from within NetWare Control Center by selecting the 'Change Password' button in the User Information screen when the user is logged in as himself/herself. Users can even change it so they have no password by pressing the 'RETURN' key when prompted for their new password even though the 'Require Password' restriction in Syscon is set to 'yes.' ISSUE/PROBLEM Apparently, NetWare Control Center does not correctly reference the account restrictions/password restrictions established in Syscon. This problem occurs with NetWare Control Center versions 2.1 and 2.11 and with NetWare for Macintosh v3.0 and v3.01. It does not occur with NetWare for Macintosh v2.2. SOLUTION Currently, there is no solution to this problem. You may wish to consider installing NetWare Control Center only on those Macintosh work stations where the user is a Supervisor or Supervisor equivalent and the user is aware of the limitations of the NetWare Control Center 'Change Password' option. FYI: NBP Type LaserShared and 'ESP' QMS Printers FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NBP Type LaserShared and 'ESP' QMS Printers DOCUMENT ID#: FYI.W.0132 DATE: 29APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0x SUPERSEDES: NA SYMPTOM: At the File Server Console, user issues the ATPSHIDE command to hide a QMS 410 printer, but the printer will not stay hidden. The following error message occurs: 'ATPS: Warning! Printer <Printer_Name> unexpectedly not hidden.' ATCON Lookup Test shows the printer's type as LaserWriter. ISSUE/PROBLEM When the ATPSHIDE command is issued or the '-h' option is used in ATPS.CFG, the NBP type of the printer is supposed to be changed from type 'LaserWriter' to 'LaserShared.' Certain QMS printers have problems with this and do not change their NBP type. The QMS printers which will have this problem are those which incorporate QMS's ESP (Emulation Sensing Processor) technology. ESP enables the printer to analyze incoming file data and then automatically select ('AutoSwitch' to) the appropriate printer language - PostScript or PCL. The following printers use 'ESP' and will have problems when ATPSHIDE tries to change the NBP type to LaserShared:QMS PS2000QMS PS1700QMS PS410QMS PS815 /The QMS PS800, PS810, and PS820 do not have this problem and can be hidden without difficulty. SOLUTION QMS Engineering is aware of this problem and is currently working on correcting it. QMS Technical Support can be reached at 205-633-4500. FYI: ClearPhantom Error Message FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ClearPhantom Error Message DOCUMENT ID#: FYI.W.0131 DATE: 29APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0x SUPERSEDES: NA SYMPTOM: Server abends with the error "ABEND: ClearPhantom called with not primary directory number running process AFP." When the server is restarted, the following error occurs "Mount VOLUME_NAME = directory block refers to non-subdirectory directory entry" and NetWare will not mount the volumes. ISSUE/PROBLEM This is not the same error that occurs in NetWare v3.10 so do not use the DELDIRFX.NLM patch.In NetWare v3.11, this error occurs when the OS is referencing a certain directory and, at the same instant, that particular directory is not available (most likely it was deleted). This is a very infrequent condition that should very rarely occur. The volumes will not mount since the server was not shutdown in a proper manner (it abended), and it is very likely that the File Allocation Table (FAT) and or Directory Entry Table (DET) may have been damaged. SOLUTION Run VREPAIR and load V_MAC.NLM (since the volume has Macintosh Name Space added) to repair the damage to the volume's File Allocation Table (FAT) and Directory Entry Table (DET) entries. FYI: 3C507 Configuration Information for the v3.11 File Server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: 3C507 Configuration Information for the v3.11 File Server DOCUMENT ID#: FYI.W.0130 DATE: 28APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When re-starting the v3.11 server, the 3C507 driver prompts the user to select a frame type (for the reentrantly loaded driver), even though the frame type had been specified on the LOAD line in AUTOEXEC.NCF. After manually selecting the appropriate frame type, the driver loaded and connectivity was established. ISSUE/PROBLEM The 3C507 driver absolutely requires a memory location entry. The first LOAD line for the IPX LAN driver specified MEM=D000, but the second line (for the AppleTalk LAN driver) had no memory parameters specified. SOLUTION After adding the memory parameters to the driver's load line in AUTOEXEC.NCF (MEM=D000 in this particular case), the server could be re-started and would initialize without asking for user input. So, just remember this:When using the 3C507 v.2.44 driver, be sure to specify ALL of the parameters (including memory parameters) on EVERY LOAD line. There apparently is no support for "default" values (at least for the memory parameters). FYI: PageMaker 4.2 and NetWare for Macintosh queues FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: PageMaker 4.2 and NetWare for Macintosh queues DOCUMENT ID#: FYI.W.0129 DATE: 28APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.x and v3.x SUPERSEDES: NA SYMPTOM: Printing from PageMaker 4.2 to the NetWare queues is extremely slow, fonts are downloaded each time a print job is sent. ISSUE/PROBLEM Aldus changed the structure of the queries the Aldus print driver uses to get information from printers on fonts, proc sets, and some others. This will be seen in the form of all fonts being downloaded to the NetWare for Macintosh queues (VAPs and NLMs) because the Aldus driver expects a different format of the font list. Prior to 4.2, Aldus used the same format as the Apple LaserWriter driver and everything worked correctly. SOLUTION VAPs (a) Use the Apple LaserWriter driver instead. This is accomplished by holding down the command-option key before selecting "Print" from the File menu. Note: Some special PageMaker printing features may not work, but most jobs should print properly. (b) Change the PostScript options within the Aldus driver in the following manner: (1) If all fonts are resident on the printer:Turn off the "Download bit-mapped fonts" and "DownloadPostScript fonts" options. (2) If some fonts must be downloaded to the printer:Turn off the "Download PostScript fonts" option.NLMs Same as VAPs, or setup a duplicate queue, but use the -o option to name it something like -o "PageMaker 4.2 queue" and use the -f option to specify a font file name that has been formatted the way the Aldus driver expects to receive the font list. This format would need a "/" character in front of each font; for example: /NewCenturySchlbk-Italic/Bookman-LightItalic/Helvetica/Courier-Bold/Helvetica-Narrow-Bold/Courier-BoldOblique/Times-Italic FYI: Macintosh can't login to v2.2 NetWare Server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh can't login to v2.2 NetWare Server DOCUMENT ID#: FYI.W.0128 DATE: 25APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: After the servers rebooted from a power failure, the Macintosh can no longer login to a v2.2 server but the DOS workstation can. ISSUE/PROBLEM The configuration was a v2.2 server with the Macintosh VAPs running phase II and a v3.11 server with the Macintosh NLMs running phase II. When the v2.2 server boots up and the Macintosh VAPs load, they will dynamically assign themselves a net number from within the phase II net number range configured on an Appletalk Router if there is one on the network. If the v2.2 server boots before any Appletalk Router boots or if there is no router, The VAPs will assign net 65280 to itself. The reason the Macintosh couldn't login to the server is because the v2.2 server would boot faster than the v3.11 server (which was configured to route AppleTalk packets) and not assign itself a valid net number from the net number range configured on the v3.11 server, it would default to 65280. The VAPs did what they were supposed to do because there was no other Appletalk Routers on the network at that time. SOLUTION Make sure the v2.2 server boots up AFTER any other Appletalk Router, use the SHOW command to verify the server has a valid net number from within the phase II range of net numbers configured on the Appletalk Router. FYI: SMC Ethercard/Plus not working with Phase I or Phase II. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: SMC Ethercard/Plus not working with Phase I or Phase II. DOCUMENT ID#: FYI.W.0126 DATE: 23APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: Two servers running NetWare v3.11 and NetWare for Macintosh v3.01 were connected via two SMC EtherCard Plus (10baseT) Ethernet cards. When executing a Lookup Test in ATCON, the servers could not see each other. PCs were able to login via the same cards. The two servers could not see each other through the AppleTalk protocol. ISSUE/PROBLEM The SMC EtherCard Plus driver v2.3 does not work well with NetWare for Macintosh. SOLUTION A newer SMC EtherCard Plus driver (v4.0) was obtained from SMC, which fixed the problem. FYI: NetWare UAM and System 7.0.1 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare UAM and System 7.0.1 DOCUMENT ID#: FYI.W.0124 DATE: 22APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: When trying to login to a Novell file server through the NetWare User Authentication Method(UAM) and the Macintosh has System 7.0.1 the Macintosh will receive the error:"An unknown error occurred of type 1" ISSUE/PROBLEM This is a bug with the AppleShare UAM utility that was used to write the NetWare UAM. SOLUTION Currently the only patch is to get AppleShare 3.0 from Apple when it becomes available. FYI: How to turn off AppleTalk error messages at the server console or system error log. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: How to turn off AppleTalk error messages at the server console or system error log. DOCUMENT ID#: FYI.W.0123 DATE: 16APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: How can AppleTalk error messages be turned off? For example, when a segment of a large network goes down, there can be many RTMP timer warnings filling up the system error log. On a network with a large number of AppleTalk nets, this can become a problem. ISSUE/PROBLEM Loading ATCON with a -L option (load ATCON -L) will add a new menu item to the ATCON menu, "Set Logging Bits". You can then go into that menu item and set 'yes' and 'no' flags for sending Fatal, Error, Warning, Info, or Verbose type messages to either the server console or the system error log. SOLUTION Load ATCON with the -L option and set the error message flags as preferred. FYI: AFPSPG Abend: Client side failed to initialize maximum socket count. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AFPSPG Abend: Client side failed to initialize maximum socket count. DOCUMENT ID#: FYI.W.0108 DATE: 16APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: The following error message was displayed on the server console when booting the server and loading the Macintosh VAPs; "AFPSPG Abend: client side failed to initialize maximum socket count." This error would not occur if the Macintosh VAPs were not loaded. ISSUE/PROBLEM The above error message is preceded by the following message "AFP Gateway: configuration file ATFILES.CFG not found". The ATFILES.CFG file is a hidden file found in the SYS:LOGIN directory. If that file is not there, the above messages are displayed and the server won't boot when loading the Macintosh VAPs. SOLUTION 1. Reboot the server without loading the Macintosh VAPs. 2. Login to the server from a DOS workstation and go into SYS:SYSTEM. 3. Delete all the Macintosh VAPs (delete *.v*, watch out for other VAPs.) 4. Make a copy of the AUTOCFG.VAP by typing the following: copy AUTOCFG.HLD AUTOCFG.VAP.5. Down the server and reboot (AUTOCFG.VAP will load and configure).6. Down and reboot again (All Macintosh VAPs will load).The AUTOCFG VAP will create a new ATFILES.CFG file, which will eliminate the above error messages. FYI: Linotronic Imagesetters FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Linotronic Imagesetters DOCUMENT ID#: FYI.W.0120 DATE: 15APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: When trying to print to Model 30 and Model 40 Linotronic ImageSetters, which are configured via an EtherTalk interface, DOS graphic-intensive files are printed with garbled data. Macintosh graphic files will print fine, as does DOS data files. ISSUE/PROBLEM Both Model 30 and Model 40 Imagesetters need a ROM upgrade to handle DOS graphics files. SOLUTION Contact Linotype-Hell for a printer ROM upgrade to Version 52. This ROM upgrade will solve this printing problem as well as correct other miscellaneous PostScript problems. FYI: ATPS Fatal Queue Error 152 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS Fatal Queue Error 152 DOCUMENT ID#: FYI.W.0119 DATE: 15APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When loading ATPS with the -d option to create a specified directory to contain all ATPS queues, ATPS reports "Fatal Queue Error" followed by "Unknown Error 152". ISSUE/PROBLEM By default, ATPS print queues will reside under SYS:\SYSTEM\ATPS. The first time the ATPS module is loaded, it creates the ATPS directory below SYS:\SYSTEM with a subdirectory for each queue configured in ATPS.CFG. If a different volume and/or directory is chosen to store ATPS queues, the -d option should be used at the LOAD command line. This new path will remain in ATPS's memory until another path to store the print queues is specified. If the queue subdirectory has already been created using the DOS MD (Make Directory) command, ATPS will report the above message when it tries to create the queue directory. SOLUTION If a different path is chosen to store the print jobs, this new path needs to be specified to ATPS using the -d option. If the default directory, SYS:\SYSTEM\ATPS is chosen, only specifying the -d, with no path is needed to redirect ATPS to store the queue information back to the default directory. Do not create the directory with the DOS MD command before redirect. FYI: Avatar's TokenTalk Driver FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Avatar's TokenTalk Driver DOCUMENT ID#: FYI.W.0118 DATE: 15APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: If Print Monitor is turned on, and a Macintosh workstation submitted a print job, other Macintoshes on the network would randomly lose their connection to the file server. If Print Monitor was not turned on and print jobs were submitted, all work stations remained connected to the network. The Macintoshes that would lose their connections were using older versions of Avatar's TokenTalk driver. ISSUE/PROBLEM Older versions of Avatar's TokenTalk driver do not relay correct information to some system software structures, including Print Monitor. SOLUTION Contact Avatar for an upgrade to v5.1 of their TokenTalk driver. FYI: AFPFIX4 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AFPFIX4 DOCUMENT ID#: FYI.W.0117 DATE: 13APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: When logging into the NetWare for Macintosh v3.01 server from a DOS workstation using Farallon's PhoneNet Talk, the directory names are truncated and the files will not display. ISSUE/PROBLEM This is a compatibility issue between Farallon's product and NetWare for Macintosh. SOLUTION There is a patch called AFIX4.ZIP on NetWire in NOVLIB 1 or 8, or in the NSEPro that resolves this problem. The patch includes a README that will explain how to use it. This patch has been developed only for v3.01 NetWare for Macintosh. Previous versions of NetWare for Macintosh may display the same symptoms, so users should upgrade to the current version of NetWare for Macintosh and then apply the patch. FYI: AFPFIX2 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AFPFIX2 DOCUMENT ID#: FYI.W.0116 DATE: 13APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When a backup is done of the file server, the Macintosh work stations connected to the server using the System 7.0 Macintosh OS lose their connection. ISSUE/PROBLEM Some backup systems close the bindery on the server while the backup is running. A Macintosh running System 6.x will continually query the server until the bindery is open again. A Macintosh running System 7.x will only query the server a few times and if the bindery isn't opened the Macintosh will loose its connection. SOLUTION There is a patch called AFIX2.ZIP on NetWire in NOVLIB 1 or 8, or in the NSEPro that resolves this problem. The patch includes a README that will explain how to use it. FYI: AFPFIX1 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AFPFIX1 DOCUMENT ID#: FYI.W.0115 DATE: 13APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: Copying a folder containing files into a drop box fails. ISSUE/PROBLEM This is a known problem with NetWare for Macintosh v3.0 and v3.01 and both System 6.x and 7.x Macintosh work stations. SOLUTION There is a patch called AFIX1.ZIP on NetWire in NOVLIB 1 or 8, or in the NSEPro that resolves this problem. The patch includes a ReadMe that will explain how to use it. There was a previous version of AFPFIX1 that resolved this problem, but only for System 6.x Macintosh work stations. Make sure you have the AFPFIX1.NLM dated 2/6/92 to resolve the problem on both System 6.x and 7.x Macintoshes. FYI: ATPSFIX2 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPSFIX2 DOCUMENT ID#: FYI.W.0114 DATE: 13APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: When printing to the NetWare for Macintosh queue there are errors generated like, "[ Error: syntaxerror; OffendingCommand: --nostringval-- ]" and the job will fail. ISSUE/PROBLEM This is a problem with the new Apple LaserWriter v7.1 driver. SOLUTION There is a patch called ATPS2.ZIP on NetWire in NOVLIB 1 or 8, or in the NSEPro that resolves this problem. The patch includes a README that will explain how to use it. FYI: ATPSFIX1 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPSFIX1 DOCUMENT ID#: FYI.W.0113 DATE: 13APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: The server will crash with ATPS v3.01 loaded. ISSUE/PROBLEM There is a known problem with v3.1 ATPS.NLM that comes with NetWare for Macintosh v3.01. The server will crash running process ATPS, Steams Q Runner, or AppleTalk stack process. The problem is generally experienced when printing documents that claimed that they were Adobe Document Structuring Convention compliant, but which in fact were incorrect in their compliance. SOLUTION There is a patch called ATPS1.ZIP on NetWire in NOVLIB 1 or 8, or in the NSEPro that resolves this problem. The patch includes a README that will explain how to use it. FYI: Loops in an AppleTalk Network FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Loops in an AppleTalk Network DOCUMENT ID#: FYI.W.0112 DATE: 13APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: Devices appear and disappear from the Chooser on the Macintosh client ISSUE/PROBLEM This can be caused by many problems. A common configuration problem would be to include loops in the AppleTalk network. A physical loop in an AppleTalk network may work, although it is not recommended. The reason this is not recommended is because for each AppleTalk router, the AppleTalk traffic doubles due to RTMP packets. Also on a Phase 1 network routing problems can occur because a Phase 1 Macintosh only routes packets to the last place it received an RTMP packet from. This makes it possible for a packet to have to travel all across the network to reach its destination. This would explain why some networks will show zones, printers, or servers coming and going from the Chooser when there is a loop in the network. The network is so busy it can't reliably deliver packets. Although the NetWare for Macintosh router will work in a loop, many third party routers may not work reliably. For example, when a FastPath is set for Phase 1 it will report errors repeatedly when there is a loop in the network. This can cause other routers to misfunction (like Apple's Internet Router). SOLUTION Do not use loops in the AppleTalk network. FYI: 3270 LAN Workstation for Macintosh and Mod 5 Support FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: 3270 LAN Workstation for Macintosh and Mod 5 Support DOCUMENT ID#: FYI.W.0111 DATE: 06APR92 PRODUCT: 3270 LAN Workstation for Macintosh PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM: When attempting to login to a host using a Mod 5 session, and the Macintosh workstation is utilizing a dual-monitor or 19" or larger monitor, the application will hang. Using a Mod 5 configured session is fine on a standard Macintosh monitor. ISSUE/PROBLEM There is a problem with the way the application emulates a Mod 5 session window. SOLUTION Contact Novell's Macintosh Technical Support for a revision. This problem is solved in subsequent releases of the product. FYI: Cannot Save Fontographer files to the NetWare server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Cannot Save Fontographer files to the NetWare server DOCUMENT ID#: FYI.W.0121 DATE: 04APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM: When trying to save an existing Fontographer file after opening it to make changes, the following error is returned on the, Macintosh: "Cannot save font onto file '<filename>' (duplicate file name)". ISSUE/PROBLEM Fontgrapher, by Altsys, was not designed to work in a file server environment. SOLUTION To avoid this scenario, the application should be run on the Macintosh hard drive, changes made there, and then copy the newly saved files, at the Finder level, to the server for storage. There is no current fix available from Altsys Corporation. FYI: Volume not in Chooser FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Volume not in Chooser DOCUMENT ID#: FYI.W.0110 DATE: 03APR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: The server's volume won't show up in the Chooser. ISSUE/PROBLEM If the Macintosh name space is not added to the volume, the volume will not appear to the Macintosh client. SOLUTION Add the Macintosh name space with the ADD NAME SPACE MACINTOSH TO <vol name>. The AFP.NLM must be reloaded once the name space is added. FYI: Incorrect Grace Login Message Displayed on Macintosh Workstation FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Incorrect Grace Login Message Displayed on Macintosh Workstation DOCUMENT ID#: FYI.W.0107 DATE: 26MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: User logging in from a Macintosh workstation receives a message that their password has expired and that they have 255 grace logins remaining. The 255 grace login number does not increment as the user keeps logging in. ISSUE/PROBLEM The AFPFIX3.NLM allows Macintoshes to receive a notification message when a grace login is used.When using the AFPFIX3.NLM patch on the File Server, this error will occur with the Force Periodic Password Changes option in Syscon-Account Restrictions set to YES, but the Limit Grace Logins options set to NO. When the password expiration date arrives, NetWare for Macintosh displays this incorrect message saying there 255 grace logins remaining when in fact the Limit Grace Logins option has been turned off. SOLUTION Disregard the 'Grace Login' portion of the error message. Or set the 'Limit Grace Logins' option in Syscon-Account Restrictions to YES, and NetWare for Macintosh will display the correct number of grace logins remaining. FYI: Server reboots FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Server reboots DOCUMENT ID#: FYI.W.0137 DATE: 25MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: The 3.11 server reboots when a Macintosh copies files to the server. ISSUE/PROBLEM The server's hardware configuration included a DTC controller. The DTC controller does not function properly in a Macintosh environment. SOLUTION The DTC SCSI controller was the identified as the area of fault, when it was replaced with another vendors SCSI controller everything worked as it should. FYI: Atalk error message FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Atalk error message DOCUMENT ID#: FYI.W.0106 DATE: 25MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: A customer noticed the following error message in their system error log, "Atalk warning: severity 1, 0XFE Bad dst socket" ISSUE/PROBLEM This error indicates that an application tried to send a packet to an illegal DDP destination socket, 0XFE which is socket 254. In our implementation of the Appletalk stack, socket 254 is illegal Possibly an application could not find an open socket and just happened to pick socket 254. SOLUTION This should be a rare error message and since the severity was 1, which is only a warning, it is nothing to worry about. FYI: Finder imposed volume size limitations FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Finder imposed volume size limitations DOCUMENT ID#: FYI.W.0105 DATE: 24MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: The Macintosh cannot save file(s)/folder(s) to the NetWare server because the volume is reportedly out of space. But it is known that there is plenty of space on this LARGE volume. Furthermore, other absurd file statistics (like negative file sizes) are reported by the Macintosh FINDER. ISSUE/PROBLEM The problem appears to be caused by the fact that FINDER treats a volume parameter variables as a SIGNED LONG INT. This variable type has 2k billion (2 gig) unique values. So, one can thus uniquely identify 2 trillion different volume sizes (from 1 byte to 2 gigabytes). Therefore, larger volumes (for example, 2.00001 gigabytes) cannot be uniquely identified, so the Macintosh FINDER reports absurd file system statistics when dealing with volumes of this size. Block size algorithms may further reduce this 2 gig volume size limit. Volumes as small as 1.3 gigabytes may have similar problems, but these reports have not been verified in the laboratory. SOLUTION At this point there is only one solution to this problem: NetWare volumes that will support Macintosh users should not exceed 2 gigabytes in size. To avoid all questions of this nature, volume sizes should not exceed 1.3 gigabytes. If the volume sizes are over 2 gigabytes, the user must reduce the volume size to eliminate this problem. This is a problem in the Macintosh FINDER. FYI: A PostScript error "NOSTRINGVAL" is generated when printing through the ATPS queue from a Macintosh client. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: A PostScript error "NOSTRINGVAL" is generated when printing through the ATPS queue from a Macintosh client. DOCUMENT ID#: FYI.W.0104 DATE: 24MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.x and v3.x SUPERSEDES: NA SYMPTOM: When printing from a Macintosh (with 5.2 LaserPrep) to a queue attached to a LaserWriter IIG, a "NOSTRINGVAL" PostScript error was reported on the banner page at the printer. The print job fails. If the printer was printed to directly it worked fine. And after that, one could print through the queue. If the printer was re-started, the same failure occurred. We had to send the job directly to the LaserWriter IIG before the queue would work. ISSUE/PROBLEM The dictionary (or server resident LaserPrep) file had somehow been corrupted. SOLUTION After deleting the *.PRS file from the SYS:SYSTEM\ATPS, power-cycling the printer, and then re-sending a print job (so the *.PRS was re-created) all printed fine. Even after re-starting the printer (so the LaserPrep had to be downloaded by ATPS) the printing worked as needed. For the future we have devised a brute force method for fixing this problem: Create a SYS:SYSTEM\PRINTER.BAT which contains a single line that deletes the SYS:SYSTEM\ATPS\*.PRS.Create a SYS:\SYSTEM\PRINTER.NCF to UNLOAD and LOAD ATPS.NLM.If the problem occurs again, verify the queues are not in use, and no jobs are waiting to be serviced. Then, invoke PRINTER.BAT to delete the dictionary (*.PDF) files. PRINTER.NCF can be invoked from the server console prompt. Finally, re-start the printer and send a print job (from a Macintosh) through the NetWare queue so the *.PRS file gets created. FYI: FINDER block size algorithmns and file size statistics FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: FINDER block size algorithmns and file size statistics DOCUMENT ID#: FYI.W.0103 DATE: 24MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: The Macintosh FINDER does not accurately report file/folder sizes for NetWare file server resident files/folders. ISSUE/PROBLEM This problem is caused by the block size allocation algorithm used by FINDER and how it differs from NetWare's method of determining the same information. NetWare allows the user to configure block sizes in the installation procedure (4k, 16k, etc...). Once this parameter has been set, a table is constructed which lists each file/folder and the disk space occupied by the file/folder. The number of entries in this table is dependent on the number files/folders on the volume, the block size (which is user configured) and the size of the volume. The Macintosh operating system uses a different algorithm. FINDER employs a fixed number (64k) of entries in it's file system table (called a BIT MAP TABLE). Therefore, the block size is largely dependent on the volume size. For example, the FINDER would AUTOMATICALLY divide a 640meg hard drive into 65,536 10k storage blocks. However, NetWare allows the USER to specify a 4k (or 16k, 32k, etc...) block size at system installation. This means that the Macintosh's FINDER has no accurate method for determining block size (and thus file/folder size) on a NetWare volume. Therefore, a file's/folder's reported volume space occupation statistics may diverge widely between the two platforms (Macintosh and native NetWare or DOS). In other words, one may save a 1k MS WORD file to the NetWare server, only to have the FINDER window report the size as 10k. One may use the GET INFO utility to find the accurate file size. Reported will be the actual file size (in parenthesis) and the occupied volume space. The file size is accurate while the occupied volume space statistic is incorrect because of the reasons reported above. On the other hand, the NetWare NDIR and FILER utilities will report the file size as 1k and will also indicate how many blocks (and bytes in the block(s)) have been used. Assuming the NetWare volume was configured to use 4k block sizes, this 1k file would occupy a single 4k block. Therefore, the NDIR and FINDER utilities should be relied on to return ACCURATE file sizes and occupied volume spaces for all files and folders on the NetWare file server's volume(s). SOLUTION If truly accurate file size statistics are needed, use either the NDIR or FILER utility. The Macintosh FINDER cannot accurately determine this information. This is the only "solution" to this "problem." In short, the differences in file sizes reported by FINDER and NDIR or FILER are direct results of the differences in file system algorithms used by the Macintosh and NetWare. FYI: DIABLO 630 EMULATION is not supported by the IIG and IIF LaserWriters FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DIABLO 630 EMULATION is not supported by the IIG and IIF LaserWriters DOCUMENT ID#: FYI.W.0102 DATE: 24MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.x and 3.x SUPERSEDES: NA SYMPTOM: The Apple LaserWriter IIG and IIF light flashes, but no job emerges from the printer when the job has been sent from the DOS workstation. In this scenario, a print job has been configured to use the DIABLO 630 EMULATION MODE. ISSUE/PROBLEM The new LaserWriter IIGs and IIFs do not support DIABLO 630 emulation. Apparently this functionality will be added in subsequent ROM versions, but the time table is not know for that addition. SOLUTION As a workaround, use the POSTTEXT MODE in the print job configuration. Appropriate PDF files are located on NetWire under NOVLIB 8 The file name is PDF.ZIP. These print devices are also bundled with the 3.01 NetWare for Macintosh product. Both the APLASER2.PDF and PSTSCRPT.PDF printer definition files provide the POSTTEXT MODE in the print job configuration (PRINTCON) utility. FYI: AppleTalk Print Server Cannot Attach to a 'Hidden' LaserWriter FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: AppleTalk Print Server Cannot Attach to a 'Hidden' LaserWriter DOCUMENT ID#: FYI.W.0101 DATE: 23MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.x SUPERSEDES: NA SYMPTOM: When APSVAP (the Macintosh Print Services VAP) tries to attach to a LaserWriter IINT, an error message occurs 'Printer type does not match queue type.' This error occurs even when the queue type has been selected correctly as 'LASERNT,' either in MacSetup or using the file server console ATTACH command. The LaserWriter IINT also shows up as 'running off-line servicing 0 queues.' However, Macintosh users can see the printer from the Chooser and can also print to it directly by bypassing the NetWare print queue. ISSUE/PROBLEM Check to see if Apple's AppleShare Print Server program is running on an AppleShare server elsewhere on the network. The AppleShare Print Server program changes the LaserWriter IINT's NBP type to LaserShared (thus making it 'hidden' from users) and advertises its AppleShare spooler with the same name that the LaserWriter IINT had previously. The Macintosh users are actually printing to the AppleShare spooler even though it appears with the same name as the LaserWriter IINT printer. When APSVAP tries to attach to what it thinks is a LaserWriter IINT (but is really the AppleShare spooler), it receives incorrect information about the printer type and fails to attach. SOLUTION If it's not needed, delete/remove the AppleShare queue using the AppleShare Print Server program, and reboot the LaserWriter IINT to return the printer to its regular NBP type of 'LaserWriter'. FYI: ATPS console commands FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS console commands DOCUMENT ID#: FYI.W.0100 DATE: 23MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: The ATPSHIDE/ATPSQUERY and ATPSSHOW commands return the error ATPS: invalid printer/spooler name < printer name > whenever I try to issue these commands. ISSUE/PROBLEM The customer was trying to use the above commands on a printer whose name began with a number like, "12 floor Printer". The above error was returned each time. The ATPS console commands will not work properly if the printers name begins with a number. SOLUTION This will be addressed in a future release. FYI: ATPSHIDE command FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPSHIDE command DOCUMENT ID#: FYI.W.0098 DATE: 19MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: ATPSHIDE command returns the error ATPS: invalid printer/spooler name < printer name > when trying to hide a printer. ISSUE/PROBLEM The customer was trying to hide the printer with the following command, ATPSHIDE "LaserWriter Plus". The above error was returned every time. The ATPSHIDE command will not allow the use of double quotes around a printer name. SOLUTION Do not put quotes around the printer name when using the ATPSHIDE command even if the printer name has spaces in it. FYI: HandsOff Init FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: HandsOff Init DOCUMENT ID#: FYI.W.0096 DATE: 17MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 and 3.01 SUPERSEDES: NA SYMPTOM: When certain workstations accessed files on a NetWare file server, users noticed that the Creator would randomly change to either DOS, Word, Excel, and WordPerfect. This caused confusion and usage problems for the users, while other users accessing the same files would not experience any problem. ISSUE/PROBLEM There is a Macintosh init available through some BBS's called HandsOff. When this system init is loaded on the Macintosh, it will arbitrarily change the Creator type to something other than the actual application that created the file. SOLUTION Do not install the HandsOff init in your Macintosh. This is applicable for Macintoshes running 6.x and 7.x. When this init is either turned off or not installed, the problem of the Creator type does not occur. FYI: System 7 TuneUp and Background Printing FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: System 7 TuneUp and Background Printing DOCUMENT ID#: FYI.W.0095 DATE: 17MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.01 SUPERSEDES: NA SYMPTOM: ATPS.CFG was configured to advertise a HPIIISI queue, being serviced by another print server other than ATPS_PSRVR. Whenever a System 7 Macintosh submitted a print job, Print Monitor would report an error message indicating that it could not find the HPIIISI queue, even though it was readily available in the Chooser. ISSUE/PROBLEM When background printing was turned off through the Chooser, this eliminated the problem, and the queue was readily available. SOLUTION Do not turn Background Printing to "on" after the System 7 TuneUp kit has been installed. FYI: ATPS and QMS PS 410 and QMS PS 815 Printers FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS and QMS PS 410 and QMS PS 815 Printers DOCUMENT ID#: FYI.W.0094 DATE: 17MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 and 3.01 SUPERSEDES: NA SYMPTOM: QMS PS 410 and PS 815 LaserWriter printers might drop off the network when connected via LocalTalk. ATPS, if loaded with the verbose option, will encounter: "Can't find printer:Retrying" messages. ISSUE/PROBLEM There is a problem with some units of these popular laser printers, where they might unexpectedly drop off the network when used over AppleTalk. SOLUTION QMS has eliminated this AppleTalk problem on currently shipping units and that users of an older PS 410 and PS 815 with this problem can request a corrected ROM from QMS technical support at 205-633-4500. FYI: 3720 LAN Workstation for Macintosh and Printing FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: 3720 LAN Workstation for Macintosh and Printing DOCUMENT ID#: FYI.W.0093 DATE: 17MAR92 PRODUCT: 3270 LAN Workstation for Macintosh PRODUCT VERSION: 1.0 SUPERSEDES: NA SYMPTOM: Trying to print to a locally attached printer might not work. Symptoms will range anywhere from the Macintosh crashing with a system error to the printer light continually blinking, with no print job emerging. ISSUE/PROBLEM One can print within the 3270 Macintosh Workstation application by selecting the Print, PrintOIA key, or the Print menu item in the File menu. The application uses as a default the Novell 3270 font. This font includes all the 3270 special characters, and are not part of the ASCII character set. There is a problem when selecting this font. SOLUTION Do not use the Novell 3270 font. Select a different font by going into "Settings" and selecting "Terminal Setup". Any other available font will not pose this printing problem. FYI: 2.2 Server can't see Agfa printer on EtherTalk. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: 2.2 Server can't see Agfa printer on EtherTalk. DOCUMENT ID#: FYI.W.0091 DATE: 17MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: PLIST console command shows the Agfa printer running off-line servicing 0 queues. ISSUE/PROBLEM The customer has NetWare 2.2 and the Macintosh VAPs. They also have a high end Agfa RIP printer that is connected via EtherTalk and LocalTalk. The printer can switch automatically between EtherTalk and LocalTalk. When the printer's name was in both upper and lower case, the printer would not be seen on EtherTalk by the Macintosh VAPs, it would however be seen on LocalTalk. The Macintoshes could also print directly to it. A packet trace revealed that the printer had a NBP (Name Binding Protocol) case sensitivity problem. When the printer was renamed to all uppercase, the Macintosh VAPs would communicate with the printer without a problem. SOLUTION Rename the printer to all uppercase. FYI: Copying files with Onfilem utility FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Copying files with Onfilem utility DOCUMENT ID#: FYI.W.0090 DATE: 17MAR92 PRODUCT: NetWare Access Server PRODUCT VERSION: v1.2 SUPERSEDES: NA SYMPTOM: When transferring a Macintosh file from the Macintosh to the server with Onfilem, the file looks like a DOS file on the server and can't be opened. ISSUE/PROBLEM There is a problem using the NetWare Access Server's ONFILEM.EXE utility to copy Macintosh files between a Macintosh and a NetWare file server. If a Macintosh application is transferred from a Macintosh to a server (3.x or 2.x), the file transfers, but when viewed by a Macintosh logged into that server, the file has become a DOS file. The file appears to be zero K in size and it can't be launched from the Macintosh. If the same file is then transferred back to the Macintosh, it will once again become a Macintosh application and can be launched without a problem. Somehow all the data in the resource fork is put into the data fork during the transfer and the opposite happens when transferred back. Onfilem will not recognize a Macintosh file on the server (shows as zero K, as if a DOS PC was viewing the file). All transfers were done using Macbinary format. SOLUTION There is no fix as of this writing. FYI: Can't logout of server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Can't logout of server DOCUMENT ID#: FYI.W.0092 DATE: 12MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 SUPERSEDES: NA SYMPTOM: User could not logout of the server by dragging the server's file cabinet icon to the trash. ISSUE/PROBLEM The customer has v3.11 and v3.0 Macintosh NLM's, and when they attempt to logout of the server by dragging the file cabinet icon to the trash, the trashcan would be highlighted but the icon would not go away. Turns out that the Macintosh had an init called MACPUKE that was causing the problem. SOLUTION Remove the MACPUKE init and you will be able to logout of the server by dragging the file cabinet icon to the trashcan. FYI: LaserWriter IIG problems FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LaserWriter IIG problems DOCUMENT ID#: FYI.W.0099 DATE: 11MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: A) The printer will disappear. The NLM (ATPS) will complain that it "can't find printer; retrying." Moreover, the LaserWriter will sometimes jump zones, and find itself in a completely different zone. B) The printer will resist any attempts to be renamed or hidden. C) If a hidden IIG has to be re-initialized (different LaserWriter preps are found in the network) it will become visible. After it is initialized, if a user has selected it on the Chooser, it will not hide again. D) If connected via EtherTalk, it has a tendency to occasionally drop long print jobs (larger than 1 Meg). ISSUE/PROBLEM Most of these symptoms have been caused by problems with the IIG EtherTalk driver. IIG printers connected through LocalTalk have not exhibited these symptoms. SOLUTION At this time Apple is working on a fix to these problems FYI: Creating a folder without Access Control FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Creating a folder without Access Control DOCUMENT ID#: FYI.W.0089 DATE: 11MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 and 3.01 SUPERSEDES: NA SYMPTOM: If a user doesn't have the Access Control right to a folder and tries to create another folder inside that folder they will get an error, You cannot create a folder in the window <folder name>, because you do not have enough access privileges, but the folder will be created anyway. ISSUE/PROBLEM The Macintosh Finder doesn't know about inherited rights, it needs to set the rights of the ancestry (the above folder) and of the folder just created. SOLUTION Currently the only solution is to grant the Access Control right to the user or use a System 6.x Macintosh. Novell is working on a solution for future releases. FYI: Copying alias, editions, or custom icons without Modify rights FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Copying alias', editions, or custom icons without Modify rights DOCUMENT ID#: FYI.W.0088 DATE: 11MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 and 3.01 SUPERSEDES: NA SYMPTOM: If a user does not have Modify rights and they try to copy an alias, edition, or use custom icons to the directory in which they don't have that right, they will get an error. The error can vary from "editions don't work the way they are suppose to work. ....." , " Creation error...."... ISSUE/PROBLEM The problem has to do with setting the Finder info flags. You need the Modify right to set the Finder info flags. Previous to System 7, the Finder info flags didn't need to be set because there was no concept of alias, editions etc... SOLUTION Currently Novell is looking into creating a patch for this. It will be fixed in future releases of NetWare for Macintosh. As a work-around include the Modify right, or use a System 6.x Macintosh. FYI: Volume not in Chooser FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Volume not in Chooser DOCUMENT ID#: FYI.W.0087 DATE: 11MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 SUPERSEDES: NA SYMPTOM: There is no volume to mount in the Chooser even though the Macintosh Name Space was added to that volume. ISSUE/PROBLEM After the Macintosh Name Space is added to the volume, the AFP.NLN must be loaded. When the AFP.NLM loads, it creates the desktop on the root of the volume and this is what allows the Macintosh workstations to mount the servers volume. SOLUTION Load the AFP.NLM after adding the Macintosh Name Space. FYI: Installing System 7.0.1 from a Server FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: Installing System 7.0.1 from a Server DOCUMENT ID#: FYI.W.0086 DATE: 11MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When running Apple's System 7.0.1 installer from a file server (3.11) you will receive the error message: "The file "filename(i.e. Chooser)" already on "Hard Drive Name" is more recent than what you are about to install. Click Continue to replace "filename" with the older version. Click cancel to leave Hard Drive Name" untouched. ISSUE/PROBLEM The problem is that NetWare evenizes the time stamp. Apple╒s installer reads that time stamp and if it is evenized it says that there is a problem in the date of the file and you will get the error message above. SOLUTION As a work-around until Apple fixes the installer scripts, a user can install the 7.0.1 on a Macintosh and copy all files into a folder. Use Apple's Personal AppleShare to enable users to log into that Macintosh and see the folder that has the 7.0.1 installer on it and install from there. FYI: Can't install NetWare for Macintosh NLM's FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: Can't install NetWare for Macintosh NLM's DOCUMENT ID#: FYI.W.0080 DATE: 11MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: The NetWare for Macintosh NLM's would not install from the NW-MAC diskette from the product install menu. ISSUE/PROBLEM The NetWare for Macintosh disk was missing its label. The disk should have a label "NW-MAC". SOLUTION Label the disk by typing Label a:at the DOS prompt. It will ask you for the label, so enter:NW-MAC FYI: Server disappears from Chooser FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: Server disappears from Chooser DOCUMENT ID#: FYI.W.0079 DATE: 11MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: Multiple servers running the NetWare for Macintosh NLM's would appear and disappear from the Chooser. ISSUE/PROBLEM Customer had two servers both running v3.11 with the v3.x NetWare for Macintosh NLM's, a simple setup with the servers connected by Ethernet. In the Chooser the servers would appear and disappear randomly. There were no errors messages on either server. But the internal AppleTalk network number from the "load APPLETLK net=50000 zone=("my_zone")" line of both servers was the same. SOLUTION The internal net numbers of each server must be unique. Change the internal net number of one of the servers to a unique number. FYI: Ehandler FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: Ehandler DOCUMENT ID#: FYI.W.0085 DATE: 10MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: I'm having problems printing to my serial or parallel PostScript printer through the NetWare for Macintosh queues, but I don't get any banner pages with errors indicating a problem. How can I get my serial or parallel PostScript printer to display PostScript error messages when trying to troubleshoot a printing problem? ISSUE/PROBLEM PostScript printers that are attached through a serial or parallel connection need to have this support turned on. By printing a file called EHANDLER.PS to the printer from a DOS workstation this support can be turned on. SOLUTION This file can be downloaded from CompuServe in Adobe's forum in library 4. The file is called EHNDLR.TXT and you must capture to the queue that supports the printer and then type:COPY EHNDLR.TXT LPT1 from the DOS workstation. This will turn on PostSript error messages on the printer. To turn this off just reboot the printer. FYI: DeskWriter or PaintWriter problem FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: DeskWriter or PaintWriter problem DOCUMENT ID#: FYI.W.0084 DATE: 09MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 or 3.01 SUPERSEDES: NA SYMPTOM: When trying to print to a queue with the PaintWriter or DeskWriter driver on my Macintosh, it hangs. ISSUE/PROBLEM If someone attempts to use the PaintWriter or DeskWriter driver with the released versions of ATPS (v3.0, v3.01) it will cause the Macintosh to hang indefinitely. The problem is that the driver was designed to send data in chunks as the printer processes it (considerably slower than spooling to the queue). The driver can't handle the queue accepting all the job data without pause for processing so it hangs the Macintosh. SOLUTION The problem is in the PaintWriter and DeskWriter driver and is not a Novell problem, but Novell may be providing a workaround in a future release of NetWare for Macintosh. FYI: Macintosh interface cards FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh interface cards DOCUMENT ID#: FYI.W.0083 DATE: 09MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: all SUPERSEDES: NA SYMPTOM: When installing an Ethernet card into the Macintosh workstation the EtherTalk icon did not appear in the Network portion of the Control Panel even when the driver was installed. ISSUE/PROBLEM If there is a problem with the mother board on the Macintosh communicating to the LAN board this will occur. The same symptom will appear if no LAN board is installed. SOLUTION Replace the Ethernet board in the Macintosh with a known working board. If the problem persists try a different slot on the Macintosh. This is usually a hardware problem with the LAN board of the Macintosh. FYI: MACPAC bug FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: MACPAC bug DOCUMENT ID#: FYI.W.0082 DATE: 09MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: all SUPERSEDES: NA SYMPTOM: There is a new compression utility call MACPAC. It will compress Macintosh files and will decompress them from a DOS workstation. This utility is used out on Business Talk or NetWare Express for upgrading to the v2.2 and v3.11 updates. There is a bug with this utility causing it not to allow the files to be uncompressed. An error will be generated indicating the file server is not AFP compatible. ISSUE/PROBLEM The problem occurs if the Macintosh Name Space is not on the SYS volume. Even if the file you are decompressing is on another volume that does have the Macintosh Name Space, SYS must have the Mac name space as well. SOLUTION The workaround is to add the Macintosh Name Space to SYS before decompressing the files. If the Macintosh Name Space is not there you will get errors when trying to decompress saying the server is not AFP compatible. FYI: Error "ATALK error (...) DDP msg is not ATP, has type 2" FYI (Note: The origin of this information may be internal orexternal to Novell. Novell makes every effort within itsmeans to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only.Novell makes no explicit or implied claims to the validity of this information.) TITLE: Error "ATALK error (...) DDP msg is not ATP, has type 2" DOCUMENT ID#: FYI.W.0081 DATE: 09MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: The server error log shows the following message, "ATALK error (...) DDP msg is not ATP, has type 2." ISSUE/PROBLEM This error indicates a packet was passed to the AppleTalk stack that did not have a valid ATP type. This would usually be a garbage packet and can indicate a hardware problem, like a bad LAN card on the network or a LAN driver problem. SOLUTION If only a few of these messages are received over a long period of time, it would not be something to be concerned about. If several messages appear in a short time period, it would be something to look into. One thing to do would be to verify the LAN drivers on the server are current. Otherwise, a packet trace of the network may need to be gathered and analyzed to find the source device of these garbage packets. FYI: Mistake in NetWare for Macintosh v3.01 Supplement FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Mistake in NetWare for Macintosh v3.01 Supplement DOCUMENT ID#: FYI.W.0109 DATE: 05MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: When using the example in the NetWare for Macintosh v3.01 supplement, ARCNET will not work with the AppleTalk protocol. ISSUE/PROBLEM There is a mistake in the supplement on page 25. The example AUTOEXEC.NCF file configuration for AppleTalk on ARCnet (figure 8) reads as follows:file server name FS-1 IPX internal net C9008CCA load TRXNET INT=2 PORT=300 NAME=ARCNET_IPXBIND IPX ARCNET NET=40LOAD APPLETLK NET=10 NAME=ARCNET_AT ZONE={"Marketing"}BIND APPLETLK ARCNET_AT NET=11 ZONE={"Marketing"}LOAD AFP. SOLUTION The correct configuration for the AUTOEXEC.NCF should read as follows:file server name FS-1ipx internal net C9008CCAload trxnet int=2 port=300 name=arcnet_ipxbind ipx arcnet_ipx net=40load appletlk net=10 zone={"Marketing"}bind appletlk arcnet_ipx net=11 zone={"Marketing"}load afp** Note the changes made to the load appletlk and bind appletlk lines. FYI: ATPS error while printing to a queue FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS error while printing to a queue DOCUMENT ID#: FYI.W.0097 DATE: 03MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.01 SUPERSEDES: NA SYMPTOM: Whenever a user tried to print to an ATPS print queue from a Macintosh, the user would see in the ATPS Verbose screen the following error "Write job to queue: No space left on device" followed on the next line with "-ATPS: aborted job 480 due to reception error". On the Macintosh screen, the error "ATPS: can't place job in queue, queue write error" also occurs. ISSUE/PROBLEM The user had his print queues defined in the ATPS.CFG file with the -a option which means that the user must be logged in via AFP and must be defined as a queue user also. They were limiting the amount of Volume/Disk space available per user. Turns out there was not enough space left on volume SYS/ for the print job to be written to the queue because of the disk space limitation imposed. SOLUTION They increased the amount of space the user was allocated for the SYS/ volume. Printing to the queue from a Macintosh worked without a problem after that. FYI: KeyServer FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: KeyServer DOCUMENT ID#: FYI.W.0078 DATE: 02MAR92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.x SUPERSEDES: NA SYMPTOM: Can't log into KeyServer. KeyServer is concurrent-use license management software for networks. KeyServer manages access to Macintosh applications much like a library. Whenever usage of a "keyed" application is below the licensed limit, a key is checked out. If all keys are in use, the launch attempt aborts, and a dialog box offer's a place for the user in a waiting queue. ISSUE/PROBLEM KeyServer shows up in the Chooser, but when you attempt to select it, a login dialog comes up. According to the vendor, this dialog should not appear in KeyServer, and indicates that the INIT can't connect to the network service. Turns out there's a bug in the Chooser that causes the Chooser not to update resources that belong to it if the network has a single named zone. When switching from the VAPs (which had no router so the only zone was "*") to the NLMs (whose router requires at least ONE zone name on non-extended networks), the problem showed up. The zone name resource in KeyAccess was not being updated. SOLUTION Change a resource in the KeyAccess program (the client part of the KeyServer package). Sassafras Software had sent it out with a zone name in that resource instead of a "*", and the Chooser didn't update it with our zone name. In KeyAccess, change the STR resource -4090, replacing the bogus name with "*", then pad the data section with zeroes to a length of 33 bytes. This was KeyServer Light version 2.3.91, KeyAccess version 2.3.9. These resources can be edited with any resource editor like Apple's ResEdit program, but users should be careful and only edit of copy of KeyServer. Resource editors can corrupt files when used improperly. FYI: Novell NL1000 & 3.11 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Novell NL1000 & 3.11 DOCUMENT ID#: FYI.W.0077 DATE: 24FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: Novell NL1000 LocalTalk card doesn't work with NetWare 3.11. ISSUE/PROBLEM The Novell NL1000 is not supported by NetWare 3.11, due to the fact that the NL1000 has poor performance in 386/486 based computers. It is supported in the 286 product line. The Dayna DL2000 and DL/2 are the only supported LocalTalk cards with v3.11 NetWare. SOLUTION Customers must use a Dayna DL2000 or DL/2 card with v3.11 NetWare for LocalTalk connectivity. FYI: Can't attach printer to the queue FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Can't attach printer to the queue DOCUMENT ID#: FYI.W.0076 DATE: 20FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: I can't attach the printer to the queue. ISSUE/PROBLEM Some printers use DDP checksums when receiving packets on the network. NetWare for Macintosh v2.2 incorrectly determines the DDP checksum value so the printer will not communicate to the server. SOLUTION To resolve this problem install new ATALK and/or ATALK2 VAPs. These can be obtained from CompuServe's NetWire on NOVLIB library 8 and the patch is called ATALK.ZIP. Instructions for use are included. FYI: Can't see the NetWare for Macintosh file server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Can't see the NetWare for Macintosh file server DOCUMENT ID#: FYI.W.0075 DATE: 20FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: The NetWare for Macintosh server does not appear in the Chooser on the Macintosh client. ISSUE/PROBLEM When an AppleTalk router is on a network that advertises zones, if special characters are used for the zones names (for example: *, ^, ~, etc...) the file server will not be able to advertise itself in zones with special characters. SOLUTION There is a new version of the ATALK and ATALK2 VAPs that will allow this support of special characters in the zone name. This patch can be downloaded from CompuServe's NetWire in NOVLIB library 8, and is called ATALK.ZIP. It includes instructions on how to install. FYI: EtherPrint by Dayna FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: EtherPrint by Dayna DOCUMENT ID#: FYI.W.0074 DATE: 20FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM: Printers that are connected to the network with the EtherPrint by Dayna will appear in various zones intermittently. ISSUE/PROBLEM The EtherPrint box has a known problem that will cause this symptom. SOLUTION Dayna has developed a new v1.5 ROM to resolve this. Contact Dayna at 801-972-2000. FYI: Error "ATPS: can't login as ####" FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Error "ATPS: can't login as ####" DOCUMENT ID#: FYI.W.0073 DATE: 20FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When loading the ATPS.NLM the error "ATPS: can't login as ####" is received. ISSUE/PROBLEM The number generated in this message is a bindery number. The message itself indicates this bindery could not be accessed by ATPS and therefore can't load the ATPS NLM. SOLUTION There are many possible solutions to this problem. They include: 1. Verify the group Everyone has not been deleted. The group Everyone is required by ATPS, but does not have to include any members. 2. Make sure that login is enabled. Login is enabled by default, so only if login was disabled is this an issue. 3. Go into PCONSOLE and delete the Print Server "ATPS_PSRVR" and also delete any queues created by the ATPS.CFG file. After all of the above is completed load ATPS and all should work. FYI: Getting notification when print jobs are completed FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Getting notification when print jobs are completed DOCUMENT ID#: FYI.W.0072 DATE: 20FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: Since upgrading to v3.01 NetWare for Macintosh, my Macintosh clients receive messages every time a print job is completed. How can I turn this off? ISSUE/PROBLEM With v3.0 NetWare for Macintosh, the Macintosh client would not receive any messages regarding their print jobs. With v3.01 NetWare for Macintosh, the Macintosh client is informed when a print job is complete if the Notify init is installed. SOLUTION If you do not want to receive these messages, remove the Notify init, or disable the "Accept Messages" option from within the NetWare DA. FYI: Grace Login Notification FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Grace Login Notification DOCUMENT ID#: FYI.W.0071 DATE: 20FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When the Macintosh client logs into a server and a grace login is used there is no notification. ISSUE/PROBLEM Because NetWare for Macintosh corresponds to AppleShare specifications, the Macintosh is not notified when a grace login is used. AppleShare does not have this functionality. SOLUTION As a workaround, AFPFIX3.NLM was developed. This patch will notify Macintosh clients when a grace login is used so they may be warned they need to change their password. The Macintosh client will need to have the Notify init installed to receive these messages. The Notify init comes with NetWare for Macintosh utilities. AFPFX3.ZIP is posted to CompuServe's NetWire in NOVLIB library 8, with instructions on how to use. FYI: Macintosh print queues disappear. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh print queues disappear. DOCUMENT ID#: FYI.W.0070 DATE: 20FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM: Macintosh print queues unpublish themselves randomly. ISSUE/PROBLEM The server is running 2.15c and the 1.1 Mac VAPs and a Novell NL1000 LocalTalk card. The customer mentioned that the server has had hardware problems in the past. SOLUTION The customer discovered a bad LocalTalk cable, and upon removing it the queues have remained published. FYI: ATPS: Printing to LaserWriter II NT attached to the serial port on the server, substitutes certain characters. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS: Printing to LaserWriter II NT attached to the serial port on the server, substitutes certain characters. DOCUMENT ID#: FYI.W.0067 DATE: 14FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x SUPERSEDES: NA SYMPTOM: When printing a file from a Macintosh to an ATPS queue that services an Apple LaserWriter II NT connected to the COM1 port of the server, certain characters (bullets, quotes...) are substituted with other characters (%, U, R, etc.). When the same file is printed to the LaserWriter via LocalTalk, the proper characters are printed. ISSUE/PROBLEM When the Apple LaserWriter has its dip switches changed to communicate via the RS232 serial port, it communicates in a 7bit mode instead of 8bit when communicating via LocalTalk. When printing characters such as the bullet character or the copyright symbol, which are ASCII valued characters that are larger that 7bits, they are substituted for a lower ASCII value character. SOLUTION To switch the printer to 8bit mode print the SERIAL.PS file to the printer from a DOS workstation. This is done by capturing to the queue and then typing:COPY SERIAL.PS LPT1 SERIAL.PS comes with version 3.01 NetWare for Macintosh and is copied to sys:public on the server. FYI: ATPS: Abend: Invalid semaphore number passed to to kernel. Running process FSP #6. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS: Abend: Invalid semaphore number passed to kernel. Running process FSP #6. DOCUMENT ID#: FYI.W.0068 DATE: 13FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: When trying to create a folder on the server volume with a Macintosh, the following error is returned: "Abend: Invalid semaphore number passed to kernel. Running process FSP #6", and as a result, the server is frozen. The error message that is displayed on the Macintosh is as follows: "Unable to create folder, due to error -1072 (Session Closed)". An attempt to delete a file from the server volume causes the following error, "Directory access by unauthorized process". The DOS workstations are able to perform both functions without error. ISSUE/PROBLEM The machine had an Everex controller in it that was using Novell's standard ISA disk driver (ISADISK.OBJ 6444 bytes, 12-19-90, ISADISK.DSK 1027 bytes, 2-12-91). SOLUTION After upgrading the ISA disk driver (ISADISK.OBJ 6369 bytes, 12-9-91, ISA22.DSK 1027 bytes, 12-10-91) the problem was resolved and the Macintosh could function properly. The newer driver can be downloaded from NetWire NOVLIB Library 3, ISAREM.ZIP. FYI: ATPS: Printing through QMS PS410 using Posttext, text cut in half at the top of the page. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS: Printing through QMS PS410 using Posttext, text cut in half at the top of the page. DOCUMENT ID#: FYI.W.0066 DATE: 13FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.x, v3.x SUPERSEDES: NA SYMPTOM: When printing a DOS or ASCII text file from a DOS workstation to a QMS PS410 and using the APLASER2.PDF, the first line of the text would be cut in half at the top of the page. ISSUE/PROBLEM There are two PDFs that allow post text printing; APLASER2.PDF for Apple Laser Writers, and PSTSCRPT.PDF for third party PostScript printers. The margins used for Apple LaserWriters are different then those used for third party printers. Therefore, you must use the PSTSCRPT.PDF for third party printers. SOLUTION After changing the Device to 'PostScript Printer' by using the PSTSCRPT.PDF, the DOS text file printed with approximately 1/2" margins. This did not cut off the text. FYI: ATPS: Can't place job in queue, queue write error. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS: Can't place job in queue, queue write error. DOCUMENT ID#: FYI.W.0069 DATE: 12FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: When trying to print to an ATPS queue from a Macintosh, the following error comes up on the Macintosh: "ATPS: Can't place job in queue, queue write error". The problem only occurred on three of the Macintoshes on the network, other Macintoshes worked fine. ISSUE/PROBLEM The problem seemed to be related to which user was trying to print. After some investigating, it was found that each user was being limited to a certain amount of disk space. The users that weren't able to print had used up all their allotted disk space. SOLUTION To solve this, the users' that had used up their allotted disk space would need to delete some information, or the amount of disk space would need to be increased for that particular user. FYI:Macintosh hangs when printing to NetWare queue. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh hangs when printing to NetWare queue. DOCUMENT ID#: FYI.W.0065 DATE: 07FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.0 SUPERSEDES: NA SYMPTOM: When trying to print to a NetWare queue that has been setup with MacSetup, the Macintosh hangs with the following message: "Spooling to NetWare queue". ISSUE/PROBLEM The Macintosh is running System v6.0.2, which contains the LaserWriter v3.1 driver. NetWare for Macintosh supports LaserWriter v5.2 thru v7.0 printer drivers. SOLUTION Upgrade the Macintosh with a newer LaserWriter driver. FYI: File can't be copied error FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: File can't be copied error DOCUMENT ID#: FYI.W.0127 DATE: 05FEB92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.0 SUPERSEDES: NA SYMPTOM: When trying to copy a folder that contains an other folder with a file inside from the Macintosh to the server the error "File can't be copied because it can't be found" is generated. ISSUE/PROBLEM This is a problem in v2.0 NetWare for Macintosh. SOLUTION Upgrade to v2.2 NetWare for Macintosh. FYI: 3720 LAN Workstation for Macintosh French Code Page FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: 3720 LAN Workstation for Macintosh French Code Page DOCUMENT ID#: FYI.W.0063 DATE: 17JAN92 PRODUCT: 3270 LAN Workstation for Macintosh PRODUCT VERSION: 1.0 SUPERSEDES: NA SYMPTOM: When displaying the Keyboard after previously selecting the French Code Page, an error "3270 Emulator Error. Could not locate Resource BCEB 1609." will appear on the Macintosh workstation. ISSUE/PROBLEM There are incorrect mappings between the EBCDIC Code Resources that causes this problem. SOLUTION The fix to this problem is relatively easy through ResEdit. ResEdit is a very powerful editor utility by Apple Computers. Because the following procedures described below modify the 3270 LAN Workstation for Macintosh application, it is strongly recommended to have a backup of the application before attempting any modifications.1. With ResEdit, open the 3270 LAN Workstation for Macintosh application.2. Select the BCEB type and double-click on the module. Another pop-up window will appear with ID's ranging from 1600 to 1611.3. You will notice that ID 1609 is skipped. Select ID 1610 and do a 'Get Info' on the resource. (or, after selecting ID 1610, hold down the Apple-I key sequence.)4. In the ID field, change 1610 to 1609. Close the Get Info box on this ID by double-clicking on the small upper left-hand box.5. Select ID 1611 and do a Get Info on this resource.6. In the ID field, change 1611 to 1610. Close the Get Info box on this ID by double-clicking on the small upper left-hand box.7. Close the BCEB resource box by double-clicking on the small upper left-hand box.8. Close the 3270 LAN Workstation for Macintosh window by double-clicking on the small upper left-hand box and answer "YES" to save the changes to the application. FYI: 3720 LAN Workstation for Macintosh International Code Page FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: 3720 LAN Workstation for Macintosh International Code Page DOCUMENT ID#: FYI.W.0062 DATE: 17JAN92 PRODUCT: 3270 LAN Workstation for Macintosh PRODUCT VERSION: 1.0 SUPERSEDES: NA SYMPTOM: If selecting the EBCDIC International Code Page, the French Code Page is represented. ISSUE/PROBLEM There are incorrect mappings between the EBCDIC Code Resources that causes this problem. SOLUTION The fix to this problem is relatively easy through ResEdit. ResEdit is a very powerful editor utility by Apple Computers. Because the following procedures described below modify the 3270 LAN Workstation for Macintosh application, it is strongly recommended to have a backup of the application before attempting any modifications.1. With ResEdit, open the 3270 LAN Workstation for Macintosh application.2. Select the BCEB type and double-click on the module. Another pop-up window will appear with ID's ranging from 1600 to 1611.3. You will notice that ID 1609 is skipped. Select ID 1610 and do a 'Get Info' on the resource. (or, after selecting ID 1610, hold down the Apple-I key sequence.)4. In the ID field, change 1610 to 1609. Close the Get Info box on this ID by double-clicking on the small upper left-hand box.5. Select ID 1611 and do a Get Info on this resource.6. In the ID field, change 1611 to 1610. Close the Get Info box on this ID by double-clicking on the small upper left-hand box.7. Close the BCEB resource box by double-clicking on the small upper left-hand box.8. Close the 3270 LAN Workstation for Macintosh window by double-clicking on the small upper left-hand box and answer "YES" to save the changes to the application. FYI:NetWare for Macintosh v3.x and Farallon's Liason with a TRI-DATA Token Ring board FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare for Macintosh v3.x and Farallon's Liason with a TRI-DATA Token Ring board DOCUMENT ID#: FYI.W.0064 DATE: 06JAN92 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When the Novell File Server boots and then a Macintosh boots on the Token-Ring network, the Macintosh will hang. In addition, the whole network is frozen. ISSUE/PROBLEM There is an anomaly in the Token-Ring driver from Tri-Data. Liason makes a Link Access Protocol (LAP) call to the driver to find out what the multicast address of the default zone is and the Token-Ring driver comes back and is incorrect. The Token-Ring driver returns to Liason the AppleTalk broadcast multicast address. This puts the Novell file server and any other Macintosh that boots up on the network in a recursive loop. SOLUTION Tri-Data has a fixed driver for this. Contact Tri-Data at 408-727-3270 FYI:Macintosh cannot see NetWare v2.2 file server in the Chooser. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOURINFORMATION only. Novell makes no explicit or implied claims to thevalidity of this information.) TITLE: Macintosh cannot see NetWare v2.2 file server in the Chooser. DOCUMENT ID#: FYI.W.0050 DATE: 30DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: When trying to login to a NetWare v2.2 file serverthrough the Chooser, the server name does not appear in the window, although the first line in the window can be selected and when clicking on OK, you are allowed to login to the server. ISSUE/PROBLEM There is a hidden file called ATFILES.CFG located in the LOGIN directory that contains information about the servers the Macintosh VAP host is advertising. If this file is missing `file server alias' then the Macintoshes on the LAN will not see the server name in the Chooser. To check the file, go to the LOGIN directory and `TYPE' out the ATFILES.CFG file. The information displayed will be similar to the following: {80,1,2} [<server-name>,<server-alias>,80,0] [<server-name>,<server-alias>,80,1] Each of the lines in square brackets shows the server name and its alias that is being advertised through Port 0 and Port 1. For the problem described above the file may look as follows: {80,1,2} [<server-name>, ,80,0] [<server-name>, ,80,1] Since the Macintosh only sees the file server by its alias name, if the alias is not there, the alias won't be visible in the Chooser, although it can be selected. The alias can be the same as the server name, which is the default when installing the Macintosh VAPs on a NetWare v2.2 server. SOLUTION Run RECONFIG at the server console and choose `Yes' to "Add, Change, or Delete Target Servers". Then choose `Change', enter file server name, then enter the file server's alias. Down the server and reboot. The changes will take effect and the server's alias name will be seen in the Chooser. FYI:Printing with PageMaker FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printing with PageMaker DOCUMENT ID#: FYI.W.0059 DATE: 16DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 SUPERSEDES: NA SYMPTOM: When printing from Aldus PageMaker v4.0 to an ATPS v3.0 queue intermittent problems occur particularly under System 7.0. Symptoms include undefined PostScript errors and ATPS errors like "ATPS: can't open dictionary file Dictary.*" or "ATPS: Proset exchange failed". ISSUE/PROBLEM This problem occurs when users are including the Aldus Prep file with the print jobs. SOLUTION To resolve this problem upgrade to v3.01 NetWare for Macintosh or choose not to use the Aldus Prep file. This can be done by selecting "Print..." dialog box from within PageMaker v4.0 and then selecting the "PostScript..." button. One option in the resulting window is "Make Aldus Prep permanent" and this should not be selected. Now when this job prints the Aldus Prep file will not be included. FYI:New PATCHMAN.NLM and NetWare for Macintosh Patches FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: New PATCHMAN.NLM and NetWare for Macintosh Patches DOCUMENT ID#: FYI.W.0058 DATE: 16DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 SUPERSEDES: NA SYMPTOM: When trying to use the PAPFIX1, PAPFIX3 or AFPFIX patch NLMs for NetWare for Macintosh v3.0 the user can't first load the PATCHMAN.NLM because a different version of PATCHMAN is already loaded. ISSUE/PROBLEM There are two versions of PATCHMAN.NLM but only one can be loaded on the server at a time. If other patches currently loaded on the server work with v2.20 PATCHMAN.NLM you can't load the old PATCHMAN.NLM that works with the PAPFIX1, PAPFIX3 and AFPFIX patches on the same server at the same time. Also the new PATCHMAN is not backwards compatible. SOLUTION To resolve this problem upgrade to v3.01 NetWare for Macintosh. With 3.01 version of NetWare for Macintosh these fixes are included. There will be new versions of PAPFIX1, PAPFIX3 and AFPFIX that will work with the v2.20 PATCHMAN in the future for customers who still use v3.0 NetWare for Macintosh. FYI:Serial Printing and NetWare for Macintosh FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Serial Printing and NetWare for Macintosh DOCUMENT ID#: FYI.W.0057 DATE: 16DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.01 SUPERSEDES: NA SYMPTOM: When connecting a LaserWriter serially to a NetWare file server or DOS workstation through ATPS and PSERVER or RPRINTER jobs sometimes don't print out and no error messages are generated. ISSUE/PROBLEM When connecting the printer serially, make sure the cable allows for two way communication. If it does not, when the printer runs out of paper it won't be able to tell the device it is connected to. This will cause jobs to be sent to the printer even though the printer can't handle them. SOLUTION Use a null modem cable to connect the printer. This will allow for 2 way communication. FYI:PSERVER.NLM and ATPS Printing FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: PSERVER.NLM and ATPS Printing DOCUMENT ID#: FYI.W.0055 DATE: 16DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: When the user sets up serial or parallel printing to a postscript printer off the NetWare server using PSERVER.NLM and ATPS.NLM nothing comes out of the printer. ISSUE/PROBLEM There is a known bug in PSERVER.NLM v1.21, the version that is shipped with NetWare 3.11. It can result in data being damaged before it gets to the printer. The result for PostScript data is the job seems to be sent fine and the printer light flashes, but nothing comes out. SOLUTION If having trouble getting printers connected through PSERVER working with ATPS.NLM v3.01, upgrade to v1.22 of PSERVER.NLM. This version of PSERVER.NLM is on NetWire in NOVA Library 6 or 16 and is called PSV122.ZIP and is also in the NSEPRO database. FYI:ODI Drivers and NetWare for Macintosh FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ODI Drivers and NetWare for Macintosh DOCUMENT ID#: FYI.W.0054 DATE: 16DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: When trying to load or bind a driver for the AppleTalk frame type and protocol various errors will be generated or the board will load and bind correctly but will not work properly with Macintosh workstations. ISSUE/PROBLEM Many users are familiar with the ODI specifications that define how vendors will write drivers to work with NetWare v3.x and multiple frame types and protocols. There are two versions of ODI, v3.0 and v3.1. With v3.0 ODI specifications, the SNAP frame type (for example ETHERNET_SNAP) is not defined. With v3.1 ODI the SNAP frame type is defined, but it is still up to each vendor as to whether they will support this or any other frame types and protocols besides IPX. SOLUTION When using a LAN board that must have AppleTalk protocol support, verify this support is included with the drivers. Even when a board is ODI compliant it may not work with the AppleTalk protocol. The boards we currently support for the NetWare server are: ETHERNET: NE1000 by Novell NE2000 by Novell NE/2 by Novell NE3200 by Novell NE/2-32 by Novell 3C503 by 3Com 3C505 by 3Com 3C523 by 3Com TOKEN RING: IBM Token Ring II, II/A, 16/4 by IBM LOCALTALK: DL2000 by Dayna DL/2 by Dayna ARCNET: RX-NET by Novell SMC PS110 Rev. B by SMC FYI:EtherPort System 7.0 Support FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: EtherPort System 7.0 Support DOCUMENT ID#: FYI.W.0053 DATE: 16DEC91 PRODUCT: EtherPort PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: The user is having problems with using the EtherPort or NAE2000 Macintosh Ethernet boards. For example when upgrading to System 7.0 on the Macintosh workstation the user needs a new driver for the EtherPort board to work. ISSUE/PROBLEM Novell no longer sells or supports the EtherPort or NAE2000 Ethernet board for the Macintosh. These boards were sold to Shiva Communications who has directed customers to Eagle Technologies. SOLUTION To resolve EtherPort issues call Eagle Technologies at 800-733-2453. FYI:Internal Network Zone Names FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Internal Network Zone Names DOCUMENT ID#: FYI.W.0052 DATE: 16DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 SUPERSEDES: NA SYMPTOM: When trying to load the APPLETLK.NLM a syntax error is generated indicating what the proper syntax for the load line is. ISSUE/PROBLEM With NetWare for Macintosh v3.01 the user has the option of using multiple zone names for the internal network. If the user puts spaces between the zones when loading at the command line, or in the AUTOEXEC.NCF, a syntax error is generated. When no spaces are used, or if the zones are defined in the ATZONES.CFG file, the APPLETLK.NLM will load fine. For example: LOAD APPLETLK NET=5 ZONE={"INTERNAL1", "INTERNAL2"} -will not work LOAD APPLETLK NET=5 ZONE={"INTERNAL1","INTERNAL2"} -will work SOLUTION To resolve this problem do not use spaces between zone names when loading the APPLETLK.NLM from the command line or the AUTOEXEC.NCF, or define zones in the ATZONES.CFG file. FYI:EtherPrint and NetWare for Macintosh Router FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: EtherPrint and NetWare for Macintosh Router DOCUMENT ID#: FYI.W.0056 DATE: 12DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: The printer intermittently can not be found by the Macintosh, or the queue will not advertise itself through NetWare for Macintosh. ISSUE/PROBLEM The EtherPrint ROM versions 1.3 or 1.4 and the EtherPrint Plus ROM versions 1.1 and 1.2 do not function properly when other AppleTalk routers are on the network. NetWare for Macintosh v3.x does function as an AppleTalk router. SOLUTION Upgrade to version 1.5 ROM for the EtherPrint or version 1.3 ROM for the EtherPrint Plus by calling Dayna Communications at 801-972-2000. FYI:PAP: write_data message too large FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: PAP: write_data message too large DOCUMENT ID#: FYI.W.0061 DATE: 06DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: Print job will not conclude. It will spend sometime in the queue, and will later be flushed out of the queue without printing. The produced warning is "PAP: write_data message too large". ISSUE/PROBLEM The ATPS NLM sometimes reads the buffer size as being -1. The computer interprets the number as being too large. SOLUTION The answer is upgrade to 3.01 NetWare for Macintosh. FYI:New 4/16 Mbps Apple/IBM Token Ring Board (Ringer) FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: New 4/16 Mbps Apple/IBM Token Ring Board (Ringer) DOCUMENT ID#: FYI.W.0060 DATE: 06DEC91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 and v3.01 SUPERSEDES: NA SYMPTOM: The Macintosh workstation freezes and sometimes it can not see the File Server. ISSUE/PROBLEM The AppleTalk stack does not properly respond to 802.2 Test/poll commands which forces the node to hang waiting for a 802.2 Test/Final reply. SOLUTION To resolve this bind the ATTOKLLC.NLM to the proper board. For Example Load TOKEN frame = token-ring name=IPX_RING bind ATTOKLLC to IPX_RING. Notice this is not the same logical board that AppleTalk is bound to. FYI: The ODI compliant Everex TP16PC performs poorly in the AppleTalk NetWare for Macintosh 3.x file server. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: The ODI compliant Everex TP16PC performs poorly in the AppleTalk NetWare for Macintosh 3.x file server. DOCUMENT ID#: FYI.W.0051 DATE: 20NOV91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.x NLM SUPERSEDES: NA SYMPTOM: When files are drag copied to or from the NetWare for Macintosh 3.x file server, the transfers can fail or performance may suffer. ISSUE/PROBLEM The driver for this NIC has performance problems when the AppleTalk frame types are assigned to it's driver. The customer reports that Everex's technical support has acknowledged the problem and is working on a solution. SOLUTION For now, the solution will be to use another certified Ethernet NIC, like the NE2000 or NE3200, or similar NIC. FYI:Incompatability between THINKC v5.0 and TCPort v2.2 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Incompatability between THINKC v5.0 and TCPort v2.2 DOCUMENT ID#: FYI.W.0046 DATE: 11NOV91 PRODUCT: TCPort ToolKit PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: The resa_start routine for the asynchronous name resolver will always fail. ISSUE/PROBLEM The problem is yet to be determined. SOLUTION There is a temporary work-around. This work-around is to change the prototype for resa_start in the res_async.h file. The second argument to resa_start is a resa_method, Change that to ■short■. This will fix the incompatability. FYI:Unpublishing Macintosh Print Queue FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Unpublishing Macintosh Print Queue DOCUMENT ID#: FYI.W.0045 DATE: 11NOV91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: The Macintosh print queue no longer shows up in the Chooser of the Macintosh. ISSUE/PROBLEM A Macintosh print queue can be unpublished through PCONSOLE by changing the option Users can place entries in queue to No under Current Queue Status. When this is set to No the print queue will no longer be advertised in the Chooser. SOLUTION You must republish the queue from the server console with the PUBLISH console command for it to be advertised in the Chooser again. FYI:Attempted Connection to Server Failed FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Attempted Connection to Server Failed DOCUMENT ID#: FYI.W.0044 DATE: 11NOV91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v1.1 SUPERSEDES: NA SYMPTOM: A Macintosh tries to login via LocalTalk and receives the error Attempted connection to server failed, please try again later. ISSUE/PROBLEM The server was configured with a Kodiak 16 bit Ethernet card and a Dayna DL2000 LocalTalk card and running the v1.1 VAPs under 2.15c NetWare. The Ethernet card was configured as LAN A and the DL2000 as LAN B. There is a conflict with the Kodiak card as LAN A when there is also a LocalTalk card installed and using v1.1 Macintosh VAPs. SOLUTION Make the DL2000 LAN A and the Kodiak Ethernet card LAN B and upgrade to the current version of NetWare for Macintosh v2.2. You must have at least v2.0 Macintosh VAPs for this to work. FYI:Texas Instruments Microlaser Printer can Cause Fatal Problems with Daynas DL2000. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Texas Instruments Microlaser Printer can Cause Fatal Problems with Daynas DL2000. DOCUMENT ID#: FYI.W.0047 DATE: 30OCT91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.01 and below (v2.x included). SUPERSEDES: NA SYMPTOM: When a Texas Instruments Microlaser printer was attached to the v3.11 NetWare File Server with v3.0 Macintosh NLMs the server would hang. ISSUE/PROBLEM The problem is communication between the Texas Instruments printer and the DL2000. Whether the system is booted as a DOS workstation or as a server the machine will hang when the Texas Instruments printer is connected. SOLUTION Take the Texas Instruments printer off the LAN. FYI:DTC 3290 EISA controller. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: DTC 3290 EISA controller. DOCUMENT ID#: FYI.W.0041 DATE: 30OCT91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: Server abends right after loading AFP. It also gets Desktop corrrupted messages for no apparent reason. ISSUE/PROBLEM The DTC 3290 EISA controller does not work well with NW 3.11. These problems range from random crashes, to corruption of Bindery, to corruption of volume itself. SOLUTION Get another controller. The DTC 3290 EISA controller has not passed certification as of this date. FYI:Message Module Causes Macintosh to Hang FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Message Module Causes Macintosh to Hang DOCUMENT ID#: FYI.W.043 DATE: 30OCT91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: Utilities v2.11 SUPERSEDES: NA SYMPTOM: Selecting the Message module in the NetWare DA causes the Macintosh to hang (under System 6.x) or give error "Not logged in to any file servers" (under System 7.0) even though you are logged in to a server. ISSUE/PROBLEM The Message module returns this error when it is loaded in conjunction with 3Com 3+file init v1.9. SOLUTION Remove the 3+file init or use an earlier revision of the 3Com init. FYI:T16/4 the DCA Irma Trac Tokentalk board. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: T16/4 the DCA Irma Trac Tokentalk board. DOCUMENT ID#: FYI.W.0040 DATE: 29OCT91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: Token connection icon disappears overnight. Connection with file server is dropped with no warning. ISSUE/PROBLEM Dca has anounced that it is a problem with their board It occurs in large networks only, and it is due to their TI TMS 380 C16PQL. chip. SOLUTION Use another TokenRing board. However, other boards (such as Tri Data's board) have the same chip. Dca is working with TI on fixing the problem. FYI:ATPS and Seiko Color Script PS FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: ATPS and Seiko Color Script PS DOCUMENT ID#: FYI.W.0042 DATE: 24OCT91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: When sending jobs to a NetWare print queue created by ATPS, the Seiko Color Script PS printer will randomly report a Printer Busy:Status Idle message, and will no longer be able to service anymore forthcoming print jobs. ISSUE/PROBLEM The Seiko Color Script PS printer has a problem with timing out after receiving so many PAP sequences. It might be able to print several jobs (depending on the file size) and will then appear to be hung. The Firmware Interpreter Version that creates this problem is PhoenixPage230 C.8A. SOLUTION By loading ATPS with the -v option, view the AppleTalk Printing Messages screen to verify that the printer is getting the Printer Busy:Status Idle message. You can also print out a test status page to verify that the Interpreter Version is PhoenixPage230 C.8A. Seiko is aware of this problem and can be contacted at 1-800-825-9711 (technical support) for a PROM upgrade. FYI: Printer and Queue name can not be the same. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Printer and Queue name can not be the same. DOCUMENT ID#: FYI.W.0038 DATE: 11OCT91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: The file server reports errors like, LaserXXXXX: Running off-line servicing zero queues, or Syntax error in create command line. ISSUE/PROBLEM If the printer and the Queue are advertising the same name their will be a conflict. SOLUTION You should name your printers and queues with INDIVIDUAL NAMES. FYI: Cheyenne backups and Mac files FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Cheyenne backups and Mac files DOCUMENT ID#: FYI.W.0039 DATE: 27SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All versions SUPERSEDES: NA SYMPTOM: Macintosh files are not backed up and restored properly when using the ARCSERVE.NLM by Cheyenne. ISSUE/PROBLEM There are two known problems: 1. If using the ARCSERVE.NLM on a v3.11 NetWare file server and backing up a 2.x remote file server, Novell's CLIB has a incompatibility that will not allow this. Novell is working on a fix to this problem. 2. If using the ARCSERVE.NLM v3.0b pre-July there is a problem backing up Macintosh files with a 0 byte resource fork and restoring them properly. This is a Cheyenne problem. SOLUTION For the first problem the SOLUTION would be to use NBACKUP that ships with v2.15c, v2.2 and v3.11 NetWare to backup both Mac and DOS files. For the second problem Cheyenne has a new version of their NLM that fixes the problem. Cheyenne can be reached at 1-800-CHEYINC. FYI: Mirrored drives problem FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Mirrored drives problem DOCUMENT ID#: FYI.W.0034 DATE: 24SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: When copying files to the NetWare server from a Mac workstation, miscellaneous errors are generated indicating there is not enough disk space when there is plenty. ISSUE/PROBLEM There are mirrored drives in the file server and one of the mirrored drives went down. The Mac name space seems to have problems with only one drive being available when there should be two. SOLUTION Bring both drives up and the problem should be resolved. FYI: Shiva Telebridge problem FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Shiva Telebridge problem DOCUMENT ID#: FYI.W.0033 DATE: 24SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: When a Mac dials into a network through a Shiva Telebridge, the Mac users currently attached to the NetWare server are kicked off. ISSUE/PROBLEM The Shiva Telebridge has a ROM problem that will cause this. A NetWare for Mac VAP server does not have this problem. SOLUTION Call Shiva at 617-252-6400 and get the ROM upgrade to resolve the problem. FYI: Problems with MicroSoft Works and NetWare for Macintosh FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Problems with MicroSoft Works and NetWare for Macintosh DOCUMENT ID#: FYI.W.0036 DATE: 13SEP91 PRODUCT: VAPs and NLM PRODUCT VERSION: v2.2 and v3.0 SUPERSEDES: NA SYMPTOM: MicroSoft Works doesn't save files to AFP servers properly. Different configuration combinations have differing failures. So, it is enough to say there are problems when saving to (and sometimes from) an AFP server (NWMAC servers are of course AFP servers). In short, files get saved as zero byte files and thus cannot be seen or opened from within the application. Finally, the files can be viewed from the finder/multifinder folder but are reportedly empty (zero bytes). ISSUE/PROBLEM Apparently versions 2.00a - 2.00d have known problems saving files to AFP servers of any kind. SOLUTION The solution (according to MS Technical Support) is to have the customer use the latest version of Works which is 2.00e. The new version can be gotten for free from MicroSoft's CompuServe forum, through MS Technical Support, or from local distributors. FYI: Long file server names or aliases cause errors preventing successful VAP loading. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Long file server names or aliases cause errors preventing successful VAP loading. DOCUMENT ID#: FYI.W.0037 DATE: 12SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: VAPs 2.2 and below SUPERSEDES: NA SYMPTOM: If a targeted server is given a name (either primary or alias) with more than 25 characters, the AFPSPG.VAP returns the following error message at server boot-up: 'AFP Gateway: Bad format in ATFILES.CFG' Subsequently, the colon prompt never returns and the AppleTalk file/print services are not available. Furthermore, one cannot re-configure this file until the server is re-booted (without loading the VAPs) as ATFILES.CFG is held open by the AFPSPG. Finally, since the colon prompt hasn't returned, one cannot use any console commands either. ISSUE/PROBLEM For some reason, AFPSPG cannot register server names longer than 25 characters. The AFP specification says the server name can be up to 32 characters. Apparently, AFPSPG.VAP cannot support this specification. SOLUTION Use fewer than 25 characters for a given server's name or alias. Since only 24 characters will show in the chooser window, this shouldn't be a problem. FYI: APSVAP: Unable to read the settings file 128 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: APSVAP: Unable to read the settings file 128 DOCUMENT ID#: FYI.W.0035 DATE: 10SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: When using 2.2 VAPs on an external router targeting a 2.2 server, an error appears on the Router console, 'APSVAP: Unable to read the settings file 128' and 'AQSVAP: Unable to read set-up file 128'. PLIST command said there were no Appletalk printers being served, QLIST showed nothing even though there were two Appletalk print queues on the server. ISSUE/PROBLEM The printers were connected via two DL2000 cards and the server was connected via a PureData Arcnet card using PureData's version 3.5 driver. The problem is with PureData's Arcnet driver. It did work with the 1.1 VAPs but seems to have a problem with the 2.2 VAPs on a Router. SOLUTION The SOLUTION was to use the Novell Turbo RX-Net Arcnet driver supplied with NetWare 2.2 for the PureData card. The PureData Arcnet card is not certified for NetWare for Macintosh. FYI: System 7 and desktop rebuild FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: System 7 and desktop rebuild DOCUMENT ID#: FYI.W.0030 DATE: 03SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: Can't rebuild the NetWare file server desktop from a System 7 Macintosh workstation. ISSUE/PROBLEM When Apple developed System 7 they removed the finder utility to rebuild the desktop on any remote volume including their own AppleShare file server. SOLUTION Rebuild the file server's desktop from a Macintosh running System 6.0.x FYI: Notify Init and DOS Mounter FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Notify Init and DOS Mounter DOCUMENT ID#: FYI.W.0029 DATE: 03SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: Performance on the Mac workstation is very slow. ISSUE/PROBLEM Both v2.1 (or older) Notify Init and the DOS Mounter init were installed in the Macintosh Sytem folder. SOLUTION There was a conflict with both this version of the Notify Init and the DOS Mounter init. Either remove one of the inits or update the Notify init. The new Notify init is available on NetWire, AppleLink, NSEPro or through Novell technical support at 800-NETWARE. FYI: Error loading AFP.NLM FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Error loading AFP.NLM DOCUMENT ID#: FYI.W.0028 DATE: 03SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v3.0 SUPERSEDES: NA SYMPTOM: The error 'Cannot find public symbol ncp process' was received everytime AFP.NLM was loaded. ISSUE/PROBLEM The server.exe file that was loading was either corrupt or the wrong version. SOLUTION Verify the version of server.exe or recopy to verify it is not corrupt. FYI: HP3SI printer and NetWare for Mac FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: HP3SI printer and NetWare for Mac DOCUMENT ID#: FYI.W.0027 DATE: 03SEP91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.0, 2.2 and 3.0 SUPERSEDES: NA SYMPTOM: The HP3SI printer will not work with NetWare for Macintosh print queues. ISSUE/PROBLEM The HP3SI printer cannot be attached via LocalTalk and that is the only way for NetWare for Mac queues to see the printer. SOLUTION HP will be releasing a LocalTalk interface card for this printer that should resolve this issue (although testing will need to be done to verify this). Until then a printer that can be attached via LocalTalk will need to be used. FYI: Mactonas.cfg file on v3.11 server FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Mactonas.cfg file on v3.11 server DOCUMENT ID#: FYI.W.0026 DATE: 26AUG91 PRODUCT: Access Server PRODUCT VERSION: 1.20 SUPERSEDES: NA SYMPTOM: You can't limit the number of Macintosh connections via Appletalk in the mactonas.cfg file to anything less than ten connections. ISSUE/PROBLEM In the mactonas.cfg file which is read when the mactonas NLM is loaded, you are supposed to be able limit the number of OnLAN/Mac connections the file server will allow between the Access Server and Macs on the Appletalk LAN, between 1-16, you can only limit between 10-16. Anything less than 10 will still result in a total of 10 connections. For example, in this sample mactonas.cfg file, ACCESS_SERVER / 6, this is supposed to only allow 6 OnLAN/Mac connections, 10 will be the total. It can be limited from 10-16 though. SOLUTION Currently your total number of connections can't be less than 10. This is a known problem that will be addressed in future releases. FYI: Address change detected for xxxx FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Address change detected for xxxx DOCUMENT ID#: FYI.W.0025 DATE: 26AUG91 PRODUCT: Access Server PRODUCT VERSION: 1.20 SUPERSEDES: NA SYMPTOM: All of my NetWare 2.X servers on the same LAN/WAN as my Access Server get the message on their console 'address change detected for xxxx', xxxx being the name of my Access Server. ISSUE/PROBLEM This is a known bug with how NetWare 2.X servers coexist with NetWare Access Server on the same LAN/WAN. This does not occur with NetWare 3.X. This is just an informational message, it does not indicate an error state. SOLUTION None as of this writing. FYI: TCPort Developer's ToolKit and Think C v4.0 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: TCPort Developer's ToolKit and Think C v4.0 DOCUMENT ID#: FY.W.0032 DATE: 16AUG91 PRODUCT: TCPort Developer's ToolKit PRODUCT VERSION: v2.0 SUPERSEDES: NA SYMPTOM: When compiling the <application>.c file in Think C v4.0, the following error is received: 'Undefined: GESTALT (lib.π, resolver.π, socket.π)'. ISSUE/PROBLEM The GESTALT commands are not available with Think C v4.0. SOLUTION Upgrading to Think C v5.0 will take care of this problem. FYI: Errors when running FoxBase with a NetWare v2.2 server. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Errors when running FoxBase with a NetWare v2.2 server. DOCUMENT ID#: FY.W.0031 DATE: 16AUG91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: NetWare v2.2 SUPERSEDES: NA SYMPTOM: When running FoxBase v2.01 for the Mac on the local hard drive and issuing the Do... command to do the Sample.prg, the program comes up fine. But then if the Compile... command is run for the Sample.prg file, the following error is returned: 'File does not exist'. Then when trying to Do... the program again, the following error is returned: 'HFS error code in Sys(21.' ISSUE/PROBLEM This scenario was tested on a variety of Macintoshes running different system versions (6.0.7 and 7.0) and different Ethernet cards. The only combination that seemed to cause the problem was when running the Macintosh LC with an Apple Ethernet card running system 6.0.7. The Macintosh LC Ethernet card from Asanté was the only card that works fine. SOLUTION There seems to be some incompatibility with the Apple Ethernet card for the Macintosh LC and FoxBase v2.01 when running with NetWare v2.2. The Asanté card works well. FYI: SMC PC500 Arcnet & Mac FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: SMC PC500 Arcnet & Mac DOCUMENT ID#: FYI.W.0022 DATE: 13AUG91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.2 SUPERSEDES: NA SYMPTOM: The 2.2 server has two SMC PC500 Arcnet cards, the Macs can login ok from LAN A, but when attempting to login from LAN B the Mac receives a dialog box that says "Attempted connection to server has failed, try again later". ISSUE/PROBLEM When the Mac was trying to login on LAN B, LAN A was not connected to anything or was connected to an active hub. There appears to be some kind of termination problem. When the LAN A was connected to a properly terminated passive hub, the Mac on LAN B could login just fine. If the cable was then disconnected from LAN A, Macs could still login to the server for about five minutes then some kind of timeout occurred and would no longer work nor would it work if the server was rebooted. SOLUTION Make sure that the cable connected to LAN A is properly terminated at a passive hub. (connecting the cable to a active hub didn't work but not all the ports were used). FYI: Microsoft Mail and NetWare DA FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Microsoft Mail and NetWare DA DOCUMENT ID#: FYI.W.0023 DATE: 31JUL91 PRODUCT: NetWareDA v2.1 PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: Mac bombs when loading the NetWare DA. ISSUE/PROBLEM Microsoft Mail and the NetWare DA conflict. They cannot run together. SOLUTION Rename Microsoft Mail and reboot. This should work. What this does is causes Mail to load before The NetWare DA loads. FYI: NetWare DA error message. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare DA error message. DOCUMENT ID#: FYI.W.0021 DATE: 29JUL91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: All SUPERSEDES: NA SYMPTOM: With a Mac SE and 4 Megs of RAM running under Multifinder, opening the NetWare DA the error "Sorry, the NetWare DA cannot get enough memory" appears. The message is still displayed but then the DA disappears. ISSUE/PROBLEM This is a bug with the NetWare DA running on a Mac SE. SOLUTION There is no fix as of this writing. FYI: Mosaic for Macintosh FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Mosaic for Macintosh DOCUMENT ID#: FYI.W.0020 DATE: 25JUL91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.0, 2.2 SUPERSEDES: NA SYMPTOM: When I try to print using Mosaic, the Macintosh responds with the following error message, "Problem with NetWare connection, There is a problem connecting. It could be with NetWare or it could be with Appleshare". ISSUE/PROBLEM The most likely problem is the user is not a valid print queue user. SOLUTION Verify in Pconsole that the user is a valid print queue user or belongs to a group that is a valid print queue user. FYI: Macintosh hangs when copying directory structure from server to Macintosh. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh hangs when copying directory structure from server to Macintosh. DOCUMENT ID#: FYI.W.0019 DATE: 17JUL91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.2 SUPERSEDES: NA SYMPTOM: When trying to copy a folder containing several sub-folders with a total of about 376K from the server to the Macintosh hard drive, the Mac hangs and never completes the copy. ISSUE/PROBLEM There was a disk protect utility called DiskLock v2.0 from Fifth Generation Systems that had been installed on the Macintosh. When this utility was removed from the Mac, the file transfer would complete successfully. SOLUTION Remove DiskLock from the system folder of the Macintosh, this version of DiskLock is not compatible with NetWare for Macintosh v2.2. FYI: Notify Init conflict FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Notify Init conflict DOCUMENT ID#: FYI.W.0018 DATE: 11JUL91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.1 NetWare for Mac Utilities SUPERSEDES: NA SYMPTOM: Mac hangs when launching the Netware DA. ISSUE/PROBLEM When trying to use the Netware DA (version 2.1 which is included with Netware for the Mac v2.2 and v3.0) the Mac hangs if the Notify init is present along with an init file called Fileguard. Fileguard is an application which protects the Desktop. SOLUTION The answer is simple, remove the Notify init from the Netware DA, or remove Fileguard from the System folder. The presence of both files creates a conflict. FYI: The NL1000 driver (1.02) disappears from the driver list in the 2.2 INSTALL program after other Microchannel drivers or devices have been selected. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: The NL1000 driver (1.02) disappears from the driver list in the 2.2 INSTALL program after other Microchannel drivers or devices have been selected. DOCUMENT ID#: FYI.W.0017 DATE: 30JUN91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.2 SUPERSEDES: NA SYMPTOM: After selecting Microcannel LAN drivers, the NL1000 driver (v1.02) will not show up in the driver list for all subsequent LAN driver selections. ISSUE/PROBLEM The NL1000 driver (v.1.02) is to be used for an ISA type NL1000.NIC. So when microchannel LAN drivers are selected before the NL1000 driver is selected, that driver won't show up in subsequent driver lists. Conversly, after selecting ISA LAN drivers, all microchannel drivers disappear from subsequent LAN driver selection lists. SOLUTION The NL1000 driver, v.100 (resident on the LAN_DRV_180 v.2.0 diskette) will show up in the available driver list of the 2.2 INSTALL program after other microchannel drivers have been selected. Users of UNCERTIFIED microchannel NICs which are compatible with the NL1000 driver (like the DayStar Digital LT200MC) should first of all realize that this card is definately NOT CERTIFIED for use in a NetWare for Macintosh file server. Subsequently, these users may be interested to know that the v.1.00 NL1000 driver will show up after selecting other microchannel drivers. However, be aware that Novell cannot support uncertified devices used in the file server. The only certified microchannel LocalTalk NIC is the Daynatalk MC adapter. This NIC uses its own driver that comes with the NIC. FYI: Print services generate VM errors at the printer FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Print services generate VM errors at the printer DOCUMENT ID#: FYI.W.0016 DATE: 20JUN91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.0, 2.2 SUPERSEDES: NA SYMPTOM: When printing a document with multiple non-resident fonts (that must be downloaded to the printer in the POSTSCRIPT job) to a NetWare for Macintosh print queue from the Macintosh, a VM error is generated. The same document prints fine when sent directly to the printer to which the queue is attached. ISSUE/PROBLEM The printer runs out of memory when trying to hold multiple fonts. SOLUTION Download ALL special fonts used to the printer's RAM and issue the QUERY command at the server console. But, this could be a problem later on if the printer's font list changes again without issuing the QUERY command. Add more Ram to the printer. A VM error indicates the printer has run short on memory. Add a hard disk to the printer and permanently download the total font list to the storage device. Then issue the QUERY command at the server console. FYI: LanStore Drivers and Duplicating Folders FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LanStore Drivers and Duplicating Folders DOCUMENT ID#: FYI.W.0015 DATE: 19JUN91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 3.0 SUPERSEDES: NA SYMPTOM: Customer is able to do a 'copy' of a folder, but not able to make a 'duplicate' of the same folder. ISSUE/PROBLEM While logged on to a 3.11 file server, the customer was able to make copies of existing folders and move them to various locations within the volume. But, while trying to make a duplicate (Command-D sequence) of the same folders, his mac would crash after duplicating 5 files. This occured on different macs, running either the 6.05 or 6.07 OS. SOLUTION By loading the Lanstor disk drivers with the 'bypass' option, the customer's problem of duplicating folders was solved. Storage Dimensions technical support said that customers should either upgrade their drivers for NetWare 3.11, or use the Bypass option if they do not upgrade. FYI: The DL2000 with a 3C503 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: The DL2000 with a 3C503 DOCUMENT ID#: FYI.W.0014 DATE: 17JUN91 PRODUCT: NetWare for Mac PRODUCT VERSION: 3.0 SUPERSEDES: n/a SYMPTOM: Upon attaching the server to the localtalk (phone-net) network, printers and other services seem to go down. ISSUE/PROBLEM The issue here is the ability to get an interupt. With the 3C503 and the DL2000 in the same machine, they cancel each others interupts out. This is due to a hardware design issue. SOLUTION The work-around/solution seems to be when loading the DL2000 make sure the interupt is set to polled mode. For example: load DL2000 int=polled port=240 name=localtalk It doesn't matter what the DL2000 hardware settings are. What this will do is enable the the DL2000 to wait for all devices to load and then pick an available interupt. FYI: Appletalk logins FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Appletalk logins DOCUMENT ID#: FYI.W.0012 DATE: 04JUN91 PRODUCT: NetWare for Mac PRODUCT VERSION: 2.0 & 2.2 SUPERSEDES: NA SYMPTOM: Userlist command shows at least two Appletalk connections but Syscon doesn't. ISSUE/PROBLEM If NetWare for Mac printing services have been installed, the Userlist command will show at least two Appletalk connections. One is from AQSVAP and the other from APSVAP. For each Appletalk print queue created, there will be an additional Appletalk connection shown with the Userlist command for a maximum of ten Appletalk connections (8 queues + the 2 printing VAPs). Syscon will not show any Appletalk connections because it looks for a specific object type from the bindery, type '1', which is the type for a plain user. Appletalk connections are of a different object type therefore they will not appear in Syscon under the user option. However, Fconsole will show the Appletalk connections under the connection option, because it looks for other bindery object types besides just the user type. SOLUTION There is no problem, just a short explanation. FYI: NetWare for Mac 2.x and System 7 FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: NetWare for Mac 2.x and System 7 DOCUMENT ID#: FYI.W.0011 DATE: 29MAY91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.x SUPERSEDES: NA SYMPTOM: Can't print from a System 7.0 Macintosh to the queue. ISSUE/PROBLEM The problem is that the System 7.0 Dictionary file is not getting properly closed. SOLUTION 1. Have everyone log out of the server. 2. Print Directly from a System 7 Mac to the LaserWriter. 3. From the System 7.0 Mac, send a print job through the queue. 4. Down the Server and bring it back up and it should work. Note: The print job that you send to the print queue may or may not print out. That doesn't matter just down the server after you wait about 3 minutes. FYI: LAP FAILURE FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: LAP FAILURE DOCUMENT ID#: FYI.W.0010 DATE: 20MAY91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: v2.x SUPERSEDES: NA SYMPTOM: LocalTalk: LAP Failure Illegal Response Type error received when using NL1000 in the file server. ISSUE/PROBLEM The cause of this problem was a bad stretch of cable AND poor termination. SOLUTION The obvious solution here is to replace the offending cable section and to properly terminate it. FYI: Changing the Packet Size used by ArcNet drivers FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Changing the Packet Size used by ArcNet drivers DOCUMENT ID#: FYI.W.0009 DATE: 20MAY91 PRODUCT: NetWare for Macintosh PRODUCT VERSION: 2.x and below SUPERSEDES: NA SYMPTOM: ISSUE/PROBLEM A number of functions/parameters in the NetWare for Mac file server/router can be affected by the packet size used by the ArcNet driver. SOLUTION The "Jumpers" utility is used to select the packet sizes (ranging between .5k and 4k) for the TRXnet driver with AppleTalk. For NetWare for Mac, the most common packet size used is 4k. Functionality issues may be introduced when using one of the other packet sizes. FYI: Dayna's EtherPrint and ATPS.NLM FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Dayna's EtherPrint and ATPS.NLM DOCUMENT ID#: FYI.W.0007 DATE: 09MAY91 PRODUCT: NetWare for Mac PRODUCT VERSION: 3.0 SUPERSEDES: NA SYMPTOM: Getting ATPS error message "Can't find printer printer-name:type:type retrying" ISSUE/PROBLEM Customer had a LaserWriter-compatible printer attached to Dayna's EtherPrint. The ATPS.NLM was able to recognize the LaserWriter as a valid AppleTalk node on the network thru ATCON but was not able to create an AppleTalk print queue. Printing directly to the printer worked fine. The ATPS.NLM reports to the configuration file that it can not find a valid printer on the network. SOLUTION The version of the EPROM in the EtherPrint box needs to be at release level1.2. Refer the customer to Dayna Communications to get the EPROM upgrade. FYI:Virex v3.0 and printing to a Macintosh print queue. FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Virex v3.0 and printing to a Macintosh print queue. DOCUMENT ID#: FYI.W.0005 DATE: 26APR91 PRODUCT FAMILY: NetWare 286 v2.15c PRODUCT VERSION: NetWare for Macintosh v1.1 SUPERSEDES: NA SYMPTOM: I am able to see and print to the queues setup through MacSetup on a Macintosh SE while running under the Finder, but when I switch to MultiFinder, I am unable to see the queues. This only occurred on a few Macintoshes, while others on the same network worked fine in either Finder or MultiFinder. ISSUE/PROBLEM The Mac SE with Virex 3.0 seemed to have a conflict with the NetWare printing queues under Multifinder. SOLUTION When I re-installed the Macintosh system on these Macs and hadn't loaded the Virex software yet, I was able to see and print to the queues under either Finder or MultiFinder. FYI:Packet Size and the SMC PC 550 ArcNet NIC FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Packet Size and the SMC PC 550 ArcNet NIC DOCUMENT ID#: FYI.W.0004 DATE: 20FEB91 PRODUCT: NetWare for Mac PRODUCT VERSION: 1.1, 2.0 SUPERSEDES: NA SYMPTOM: When both the print AND file services are installed, the APS and AQS VAPs report an inability to open/read the settings files ->128. Error 128 is a "file in use error" so on the surface, it looks as though the print service VAPs are competing for the use of the settings file. However, the file services work fine as do the print services if each is loaded in the absence of the other. ISSUE/PROBLEM The SMC 2.13 TURBO driver allows the user to select the packet size to be used. There are four options ranging from a .5k packet size to a 4k packet size. When the .5k packet size is used, this printing failure occurs. SOLUTION When the 4k packet size was used, both the file AND print services worked concurrently in the same bridge Machine. The two other packet sizes were not tested. Also this may be applicable to other ArcNet drivers which provide configurable packet sizes. FYI:Macintosh Unable to See File Server on LOCALTALK FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: Macintosh Unable to See File Server on LOCALTALK DOCUMENT ID#: FYI.W.0002 DATE: 15JAN91 PRODUCT: NetWare for Mac PRODUCT VERSION: 2.0 SUPRESEDES: NA SYMPTOM: The file server doesn't show up under LOCALTALK. ISSUE/PROBLEM When the network was set to ETHERTALK both file servers would show up in the chooser, as well as the printer. The user could login and print a job to the printer through the queue. When the network was set to Built-in, neither of the file servers would show up in the chooser, but the queue and the LASERWRITER name could be seen and a job could print to the queue or LASERWRITER. SOLUTION The user set the interrupt of the DL2000 "Polled". Once this was changed to IRQ3 the file servers showed up in the chooser under Built-in (LOCALTALK). Apparently the AFPSPG will not work with a card set with an IRQ "Polled". FYI:The Tiara 16-bit Micro Channel Arcnet Card FYI (Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.) TITLE: The Tiara 16-bit Micro Channel Arcnet Card DOCUMENT ID#: FYI.W.0001 DATE: 15JAN91 PRODUCT: NetWare for Mac PRODUCT VERSION: 2.0 SUPERSEDES: NA SYMPTOM: Can't get the NetWare services advertised on the LOCALTALK LAN supported by a DL/2. ISSUE/PROBLEM When trying to use the Novell Turbo RX-NET driver with APPLETALK to drive the Tiara MC Arcnet card, everything works fine if the NetWare services are to be advertised on the Arcnet LAN only. But, when the LOCALTALK LAN is added, the file server would at times not recognize both drivers (the TRX-NET and DL/2) at the same time. Other times both drivers would load, but no LOCALTALK services were available to the NetWare users. The APPLETALK printing was inoperable, and there were no file services available to the Mac's on LOCALTALK. SOLUTION Since Tiara does not have a released version of the Arcnet driver supporting APPLETALK, the only solution at this time is to use another card that will either use our TRX-NET driver with APPLETALK, or has an APPLETALK supporting driver of its own.